Part Number Hot Search : 
710AS NC7NZ04 NCP15 NCP15 NCP15 VTT7123 Z102X NCP15
Product Description
Full Text Search
 

To Download 68HC08AS32 Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
 Order this document by MC68HC08AS32/D Rev. 3.0
68HC08AS32
Advance Information
This document contains information on a new product. Specifications and information herein are subject to change without notice.
NON-DISCLOSURE
AGREEMENT
HC08
REQUIRED
Advance Information REQUIRED AGREEMENT
NON-DISCLOSURE
Motorola reserves the right to make changes without further notice to any products herein to improve reliability, function or design. Motorola does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey any license under its patent rights nor the rights of others. Motorola products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other application in which the failure of the Motorola product could create a situation where personal injury or death may occur. Should Buyer purchase or use Motorola products for any such unintended or unauthorized application, Buyer shall indemnify and hold Motorola and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Motorola was negligent regarding the design or manufacture of the part.
Advance Information 2
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
List of Sections
Section 1. General Description . . . . . . . . . . . . . . . . . . . 29 Section 2. Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . 43 Section 3. Random-Access Memory (RAM) . . . . . . . . . 55 Section 4. Read-Only Memory (ROM). . . . . . . . . . . . . . 57 Section 5. Mask Options . . . . . . . . . . . . . . . . . . . . . . . . . 59 Section 6. Electrically Erasable Programmable ROM (EEPROM) . . . . . . . . . . . . . . 63 Section 7. Central Processor Unit (CPU) . . . . . . . . . . . . 75 Section 8. Clock Generator Module (CGM) . . . . . . . . . 93 Section 9. System Integration Module (SIM) . . . . . . . . 121 Section 10. Low-Voltage Inhibit (LVI). . . . . . . . . . . . . . 145 Section 11. Break Module (Break) . . . . . . . . . . . . . . . . 151 Section 12. Monitor ROM (MON) . . . . . . . . . . . . . . . . . 159 Section 13. Computer Operating Properly (COP) . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Section 14. External Interrupt (IRQ) . . . . . . . . . . . . . . . 175 Section 15. Input/Output (I/O) Ports . . . . . . . . . . . . . . 183 Section 16. Timer Interface (TIM) . . . . . . . . . . . . . . . . . 205
MC68HC08AS32 -- Rev. 3.0 MOTOROLA List of Sections
Advance Information 3
NON-DISCLOSURE
AGREEMENT
REQUIRED
List of Sections REQUIRED Section 17. Serial Communications Interface (SCI). . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Section 18. Serial Peripheral Interface (SPI) . . . . . . . . 275 Section 19. Analog-to-Digital Converter (ADC) . . . . . 309 Section 20. Byte Data Link Controller-Digital (BDLC-D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Section 21. Electrical Specifications . . . . . . . . . . . . . . 371 Section 22. Mechanical Data. . . . . . . . . . . . . . . . . . . . 385 Section 23. Ordering Information . . . . . . . . . . . . . . . . . 389
NON-DISCLOSURE
Advance Information 4 List of Sections
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Table of Contents
Section 1. General Description
1.1 1.2 1.3 1.4 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 MCU Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Section 2. Memory Map
2.1 2.2 2.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Input/Output (I/O) Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents
Advance Information 5
NON-DISCLOSURE
1.5 Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 1.5.1 Power Supply Pins (VDD and VSS) . . . . . . . . . . . . . . . . . . .35 1.5.2 Oscillator Pins (OSC1 and OSC2) . . . . . . . . . . . . . . . . . . .36 1.5.3 External Reset Pin (RST) . . . . . . . . . . . . . . . . . . . . . . . . . .36 1.5.4 External Interrupt Pin (IRQ). . . . . . . . . . . . . . . . . . . . . . . . .36 1.5.5 Analog Power Supply Pin (VDDA/VDDAREF). . . . . . . . . . . . .36 1.5.6 ADC High Reference Pin (VREFH) . . . . . . . . . . . . . . . . . . . .36 1.5.7 Analog Ground Pin (VSSA/VREFL) . . . . . . . . . . . . . . . . . . . .37 1.5.8 External Filter Capacitor Pin (CGMXFC). . . . . . . . . . . . . . .37 1.5.9 Port A Input/Output (I/O) Pins (PTA7-PTA0) . . . . . . . . . . .37 1.5.10 Port B I/O Pins (PTB7/ATD7-PTB0/ATD0). . . . . . . . . . . . .37 1.5.11 Port C I/O Pins (PTC4-PTC0). . . . . . . . . . . . . . . . . . . . . . .37 1.5.12 Port D I/O Pins (PTD6/ATD14/TCLKA-PTD0/ATD8) . . . . .38 1.5.13 Port E I/O Pins (PTE7/SPSCK-PTE0/TxD) . . . . . . . . . . . .38 1.5.14 Port F I/O Pins (PTF3/TCH5-PTF0/TCH2) . . . . . . . . . . . . .38 1.5.15 J1850 Transmit Pin Digital (BDTxD) . . . . . . . . . . . . . . . . . .38 1.5.16 J1850 Receive Pin Digital (BDRxD) . . . . . . . . . . . . . . . . . .38
AGREEMENT
REQUIRED
Table of Contents REQUIRED Section 3. Random-Access Memory (RAM)
3.1 3.2 3.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Section 4. Read-Only Memory (ROM)
4.1 4.2 4.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
AGREEMENT
Section 5. Mask Options
5.1 5.2 5.3 5.4 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Mask Option Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Section 6. Electrically Erasable Programmable ROM (EEPROM)
6.1 6.2 6.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
NON-DISCLOSURE
6.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 6.4.1 EEPROM Programming . . . . . . . . . . . . . . . . . . . . . . . . . . .64 6.4.2 EEPROM Erasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 6.4.3 EEPROM Block Protection . . . . . . . . . . . . . . . . . . . . . . . . .68 6.4.4 EEPROM Redundant Mode . . . . . . . . . . . . . . . . . . . . . . . .69 6.4.5 EEPROM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .69 6.4.6 EEPROM Control Register . . . . . . . . . . . . . . . . . . . . . . . . .70 6.4.7 EEPROM Non-volatile Register and EEPROM Array Configuration Register . . . . . . . . .72 6.4.8 Low-Power Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 6.4.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 6.4.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Advance Information 6 Table of Contents
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Table of Contents
Section 7. Central Processor Unit (CPU)
7.1 7.2 7.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
7.5 7.6 7.7 7.8
Arithmetic/Logic Unit (ALU) . . . . . . . . . . . . . . . . . . . . . . . . . . .83 CPU During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . .83 Instruction Set Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Opcode Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Section 8. Clock Generator Module (CGM)
8.1 8.2 8.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
8.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 8.4.1 Crystal Oscillator Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . .95 8.4.2 Phase-Locked Loop Circuit (PLL) . . . . . . . . . . . . . . . . . . . .97 8.4.2.1 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 8.4.2.2 Acquisition and Tracking Modes . . . . . . . . . . . . . . . . . . .99 8.4.2.3 Automatic and Manual PLL Bandwidth Modes . . . . . . . .99 8.4.2.4 Programming the PLL . . . . . . . . . . . . . . . . . . . . . . . . . .101 8.4.2.5 Special Programming Exceptions . . . . . . . . . . . . . . . . .103 8.4.3 Base Clock Selector Circuit. . . . . . . . . . . . . . . . . . . . . . . .103 8.4.4 CGM External Connections. . . . . . . . . . . . . . . . . . . . . . . .104 8.5 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 8.5.1 Crystal Amplifier Input Pin (OSC1) . . . . . . . . . . . . . . . . . .105 8.5.2 Crystal Amplifier Output Pin (OSC2) . . . . . . . . . . . . . . . . .105 8.5.3 External Filter Capacitor Pin (CGMXFC). . . . . . . . . . . . . .105 8.5.4 Analog Power Pin (VDDA/VDDAREF). . . . . . . . . . . . . . . . . .106 8.5.5 Oscillator Enable Signal (SIMOSCEN) . . . . . . . . . . . . . . .106
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents Advance Information 7
NON-DISCLOSURE
AGREEMENT
7.4 CPU Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 7.4.1 Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 7.4.2 Index Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 7.4.3 Stack Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 7.4.4 Program Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 7.4.5 Condition Code Register . . . . . . . . . . . . . . . . . . . . . . . . . . .81
REQUIRED
Table of Contents REQUIRED
8.5.6 8.5.7 8.5.8 Crystal Output Frequency Signal (CGMXCLK) . . . . . . . . .106 CGM Base Clock Output (CGMOUT) . . . . . . . . . . . . . . . .106 CGM CPU Interrupt (CGMINT) . . . . . . . . . . . . . . . . . . . . .106
8.6 CGM Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 8.6.1 PLL Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 8.6.2 PLL Bandwidth Control Register . . . . . . . . . . . . . . . . . . . .110 8.6.3 PLL Programming Register . . . . . . . . . . . . . . . . . . . . . . . .112 8.7 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 8.8 Special Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 8.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 8.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 8.9 CGM During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . .115 8.10 Acquisition/Lock Time Specifications . . . . . . . . . . . . . . . . . . .115 8.10.1 Acquisition/Lock Time Definitions . . . . . . . . . . . . . . . . . . .115 8.10.2 Parametric Influences on Reaction Time . . . . . . . . . . . . .117 8.10.3 Choosing a Filter Capacitor. . . . . . . . . . . . . . . . . . . . . . . .118 8.10.4 Reaction Time Calculation . . . . . . . . . . . . . . . . . . . . . . . .119
AGREEMENT
Section 9. System Integration Module (SIM)
9.1 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 9.2
NON-DISCLOSURE
9.3 SIM Bus Clock Control and Generation . . . . . . . . . . . . . . . . .125 9.3.1 Bus Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 9.3.2 Clock Startup from POR or LVI Reset. . . . . . . . . . . . . . . .125 9.3.3 Clocks in Stop Mode and Wait Mode . . . . . . . . . . . . . . . .126 9.4 Reset and System Initialization. . . . . . . . . . . . . . . . . . . . . . . .126 9.4.1 External Pin Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 9.4.2 Active Resets from Internal Sources . . . . . . . . . . . . . . . . .128 9.4.2.1 Power-On Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 9.4.2.2 Computer Operating Properly (COP) Reset. . . . . . . . . .130 9.4.2.3 Illegal Opcode Reset . . . . . . . . . . . . . . . . . . . . . . . . . . .130 9.4.2.4 Illegal Address Reset . . . . . . . . . . . . . . . . . . . . . . . . . . .130 9.4.2.5 Low-Voltage Inhibit (LVI) Reset . . . . . . . . . . . . . . . . . . .130
Advance Information 8 Table of Contents
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Table of Contents
9.5 SIM Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 9.5.1 SIM Counter During Power-On Reset . . . . . . . . . . . . . . . .131 9.5.2 SIM Counter During Stop Mode Recovery . . . . . . . . . . . .131 9.5.3 SIM Counter and Reset States . . . . . . . . . . . . . . . . . . . . .131 9.6 Program Exception Control. . . . . . . . . . . . . . . . . . . . . . . . . . .132 9.6.1 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 9.6.1.1 Hardware Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 9.6.1.2 SWI Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 9.6.2 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 9.6.3 Break Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 9.6.4 Status Flag Protection in Break Mode. . . . . . . . . . . . . . . .136 9.7 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 9.7.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 9.7.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138 9.8 SIM Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 9.8.1 SIM Break Status Register . . . . . . . . . . . . . . . . . . . . . . . .140 9.8.2 SIM Reset Status Register . . . . . . . . . . . . . . . . . . . . . . . .142 9.8.3 SIM Break Flag Control Register. . . . . . . . . . . . . . . . . . . .143
Section 10. Low-Voltage Inhibit (LVI)
10.1 10.2 10.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
10.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 10.4.1 Polled LVI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 10.4.2 Forced Reset Operation . . . . . . . . . . . . . . . . . . . . . . . . . .147 10.4.3 False Reset Protection . . . . . . . . . . . . . . . . . . . . . . . . . . .148 10.5 10.6 LVI Status Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 LVI Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
10.7 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 10.7.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 10.7.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents
Advance Information 9
NON-DISCLOSURE
AGREEMENT
REQUIRED
Table of Contents REQUIRED Section 11. Break Module (Break)
11.1 11.2 11.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
AGREEMENT
11.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 11.4.1 Flag Protection During Break Interrupts . . . . . . . . . . . . . .153 11.4.2 CPU During Break Interrupts. . . . . . . . . . . . . . . . . . . . . . .154 11.4.3 TIM During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . .154 11.4.4 COP During Break Interrupts . . . . . . . . . . . . . . . . . . . . . .154 11.5 Break Module Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 11.5.1 Break Status and Control Register . . . . . . . . . . . . . . . . . .155 11.5.2 Break Address Registers. . . . . . . . . . . . . . . . . . . . . . . . . .156 11.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 11.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 11.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Section 12. Monitor ROM (MON)
12.1 12.2 12.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
NON-DISCLOSURE
12.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 12.4.1 Entering Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . .162 12.4.2 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 12.4.3 Echoing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 12.4.4 Break Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 12.4.5 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165 12.4.6 Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Section 13. Computer Operating Properly (COP)
13.1 13.2 13.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
Advance Information 10 Table of Contents
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Table of Contents
13.4 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.1 CGMXCLK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.2 STOP Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.3 COPCTL Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.4 Internal Reset Resources . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.5 Reset Vector Fetch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.6 COPD (COP Disable) . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.7 COPS (COP Short Timeout) . . . . . . . . . . . . . . . . . . . . . . .173 13.5 13.6 13.7 COP Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
13.8 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 13.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 13.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 13.9 COP Module During Break Interrupts . . . . . . . . . . . . . . . . . . .174
Section 14. External Interrupt (IRQ)
14.1 14.2 14.3 14.4 14.5 14.6 14.7 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 IRQ Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 IRQ Module During Break Interrupts . . . . . . . . . . . . . . . . . . .180 IRQ Status and Control Register . . . . . . . . . . . . . . . . . . . . . .180
Section 15. Input/Output (I/O) Ports
15.1 15.2 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
15.3 Port A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 15.3.1 Port A Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 15.3.2 Data Direction Register A . . . . . . . . . . . . . . . . . . . . . . . . .186 15.4 Port B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 15.4.1 Port B Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 15.4.2 Data Direction Register B . . . . . . . . . . . . . . . . . . . . . . . . .189
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents Advance Information 11
NON-DISCLOSURE
AGREEMENT
REQUIRED
Table of Contents REQUIRED
15.5 Port C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 15.5.1 Port C Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 15.5.2 Data Direction Register C . . . . . . . . . . . . . . . . . . . . . . . . .192 15.6 Port D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 15.6.1 Port D Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 15.6.2 Data Direction Register D . . . . . . . . . . . . . . . . . . . . . . . . .195 15.7 Port E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 15.7.1 Port E Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 15.7.2 Data Direction Register E . . . . . . . . . . . . . . . . . . . . . . . . .199 15.8 Port F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 15.8.1 Port F Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 15.8.2 Data Direction Register F . . . . . . . . . . . . . . . . . . . . . . . . .202
AGREEMENT
Section 16. Timer Interface (TIM)
16.1 16.2 16.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
NON-DISCLOSURE
16.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209 16.4.1 TIM Counter Prescaler . . . . . . . . . . . . . . . . . . . . . . . . . . .209 16.4.2 Input Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209 16.4.3 Output Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211 16.4.3.1 Unbuffered Output Compare . . . . . . . . . . . . . . . . . . . . .211 16.4.3.2 Buffered Output Compare . . . . . . . . . . . . . . . . . . . . . . .212 16.4.4 Pulse Width Modulation (PWM) . . . . . . . . . . . . . . . . . . . .213 16.4.4.1 Unbuffered PWM Signal Generation . . . . . . . . . . . . . . .214 16.4.4.2 Buffered PWM Signal Generation . . . . . . . . . . . . . . . . .215 16.4.4.3 PWM Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216 16.5 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218 16.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218 16.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218 16.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219 16.7 TIM During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . .219 16.8 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220 16.8.1 TIM Clock Pin (PTD6/ATD14/TCLK) . . . . . . . . . . . . . . . . .220
Advance Information 12 Table of Contents
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Table of Contents
16.8.2
TIM Channel I/O Pins (PTF3/TCH5-PTF0/ TCH2 and PTE3/TCH1-PTE2/TCH0) . . . . . . . . . . . . .220
16.9 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 16.9.1 TIM Status and Control Register . . . . . . . . . . . . . . . . . . . .221 16.9.2 TIM Counter Registers . . . . . . . . . . . . . . . . . . . . . . . . . . .224 16.9.3 TIM Counter Modulo Registers . . . . . . . . . . . . . . . . . . . . .225 16.9.4 TIM Channel Status and Control Registers. . . . . . . . . . . .226 16.9.5 TIM Channel Registers . . . . . . . . . . . . . . . . . . . . . . . . . . .231
17.1 17.2 17.3
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
17.5 Receiver Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253 17.5.1 Error Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254 17.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 17.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 17.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 17.7 SCI During Break Module Interrupts. . . . . . . . . . . . . . . . . . . .255
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents
Advance Information 13
NON-DISCLOSURE
17.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 17.4.1 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 17.4.2 Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 17.4.3 Character Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 17.4.4 Character Transmission . . . . . . . . . . . . . . . . . . . . . . . . . .241 17.4.5 Break Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 17.4.6 Idle Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 17.4.7 Inversion of Transmitted Output . . . . . . . . . . . . . . . . . . . .245 17.4.8 Transmitter Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 17.4.9 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 17.4.10 Character Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 17.4.11 Character Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 17.4.12 Data Sampling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 17.4.13 Framing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 17.4.14 Receiver Wakeup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
AGREEMENT
Section 17. Serial Communications Interface (SCI)
REQUIRED
Table of Contents REQUIRED
17.8 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256 17.8.1 PTE0/TxD (Transmit Data) . . . . . . . . . . . . . . . . . . . . . . . .256 17.8.2 PTE1/RxD (Receive Data) . . . . . . . . . . . . . . . . . . . . . . . .256 17.9 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 17.9.1 SCI Control Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .257 17.9.2 SCI Control Register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . .261 17.9.3 SCI Control Register 3 . . . . . . . . . . . . . . . . . . . . . . . . . . .263 17.9.4 SCI Status Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 17.9.5 SCI Status Register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 17.9.6 SCI Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270 17.9.7 SCI Baud Rate Register . . . . . . . . . . . . . . . . . . . . . . . . . .271
AGREEMENT
Section 18. Serial Peripheral Interface (SPI)
18.1 18.2 18.3 18.4 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Pin Name and Register Name Conventions . . . . . . . . . . . . . .277
18.5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278 18.5.1 Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 18.5.2 Slave Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281 18.6 Transmission Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 18.6.1 Clock Phase and Polarity Controls . . . . . . . . . . . . . . . . . .282 18.6.2 Transmission Format When CPHA = 0 . . . . . . . . . . . . . . .283 18.6.3 Transmission Format When CPHA = 1 . . . . . . . . . . . . . . .284 18.6.4 Transmission Initiation Latency . . . . . . . . . . . . . . . . . . . . .286 18.7 Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288 18.7.1 Overflow Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288 18.7.2 Mode Fault Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290 18.8 18.9 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292 Queuing Transmission Data . . . . . . . . . . . . . . . . . . . . . . . . . .293
NON-DISCLOSURE
18.10 Resetting the SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 18.11 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 18.11.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 18.11.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 18.12 SPI During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . .297
Advance Information 14 Table of Contents MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Table of Contents
18.13 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298 18.13.1 MISO (Master In/Slave Out) . . . . . . . . . . . . . . . . . . . . . . .298 18.13.2 MOSI (Master Out/Slave In) . . . . . . . . . . . . . . . . . . . . . . .299 18.13.3 SPSCK (Serial Clock) . . . . . . . . . . . . . . . . . . . . . . . . . . . .299 18.13.4 SS (Slave Select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 18.13.5 VSS (Clock Ground). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 18.14 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 18.14.1 SPI Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302 18.14.2 SPI Status and Control Register . . . . . . . . . . . . . . . . . . . .304 18.14.3 SPI Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308
Section 19. Analog-to-Digital Converter (ADC)
19.1 19.2 19.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
19.5
Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
19.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 19.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 19.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 19.7 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 19.7.1 ADC Analog Power Pin (VDDA/VDDAREF)/ ADC Voltage Reference Pin (VREFH) . . . . . . . . . . . . . .314 19.7.2 ADC Analog Ground Pin (VSSA)/ ADC Voltage Reference Low Pin (VREFL) . . . . . . . . . .314 19.7.3 ADC Voltage In (ADCVIN). . . . . . . . . . . . . . . . . . . . . . . . .315 19.8 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 19.8.1 ADC Status and Control Register . . . . . . . . . . . . . . . . . . .315 19.8.2 ADC Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318 19.8.3 ADC Input Clock Register . . . . . . . . . . . . . . . . . . . . . . . . .318
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents
Advance Information 15
NON-DISCLOSURE
19.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 19.4.1 ADC Port I/O Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311 19.4.2 Voltage Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 19.4.3 Conversion Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 19.4.4 Continuous Conversion Mode . . . . . . . . . . . . . . . . . . . . . .313 19.4.5 Accuracy and Precision. . . . . . . . . . . . . . . . . . . . . . . . . . .313
AGREEMENT
REQUIRED
Table of Contents REQUIRED Section 20. Byte Data Link Controller-Digital (BDLC-D)
20.1 20.2 20.3 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323
AGREEMENT
20.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324 20.4.1 BDLC Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . .326 20.4.1.1 Power Off Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 20.4.1.2 Reset Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 20.4.1.3 Run Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 20.4.1.4 BDLC Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328 20.4.1.5 BDLC Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328 20.4.1.6 Digital Loopback Mode. . . . . . . . . . . . . . . . . . . . . . . . . .328 20.4.1.7 Analog Loopback Mode . . . . . . . . . . . . . . . . . . . . . . . . .329 20.5 BDLC MUX Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329 20.5.1 Rx Digital Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330 20.5.1.1 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330 20.5.1.2 Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331 20.5.2 J1850 Frame Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . .332 20.5.3 J1850 VPW Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . .335 20.5.4 J1850 VPW Valid/Invalid Bits and Symbols . . . . . . . . . . .338 20.5.5 Message Arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343 20.6 BDLC Protocol Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345 20.6.1 Protocol Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346 20.6.2 Rx and Tx Shift Registers . . . . . . . . . . . . . . . . . . . . . . . . .347 20.6.3 Rx and Tx Shadow Registers . . . . . . . . . . . . . . . . . . . . . .347 20.6.4 Digital Loopback Multiplexer . . . . . . . . . . . . . . . . . . . . . . .347 20.6.5 State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348 20.6.5.1 4X Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348 20.6.5.2 Receiving a Message in Block Mode . . . . . . . . . . . . . . .348 20.6.5.3 Transmitting a Message in Block Mode . . . . . . . . . . . . .348 20.6.5.4 J1850 Bus Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349 20.6.5.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351 20.7 BDLC CPU Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352 20.7.1 BDLC Analog and Roundtrip Delay Register . . . . . . . . . .353 20.7.2 BDLC Control Register 1. . . . . . . . . . . . . . . . . . . . . . . . . .354 20.7.3 BDLC Control Register 2. . . . . . . . . . . . . . . . . . . . . . . . . .357
NON-DISCLOSURE
Advance Information 16
MC68HC08AS32 -- Rev. 3.0 Table of Contents MOTOROLA
Table of Contents
20.7.4 20.7.5
BDLC State Vector Register . . . . . . . . . . . . . . . . . . . . . . .364 BDLC Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . .366
20.8 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368 20.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368 20.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
Section 21. Electrical Specifications
21.1 21.2 21.3 21.4 21.5 21.6 21.7 21.8 21.9 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371 Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372 Functional Operating Range. . . . . . . . . . . . . . . . . . . . . . . . . .373 Thermal Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373 5.0-Volt DC Electrical Characteristics Control Timing . . . . . .374 Control Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375 ADC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376 5.0-Vdc 10% Serial Peripheral Interface (SPI) Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . .377 CGM Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . .380 . . . . . . . . . . . . . . . . . . . . . . .380 . . . . . . . . . . . . . . .381
21.10 CGM Component Information
21.11 CGM Acquisition/Lock Time Information
21.12 Timer Module Characteristics . . . . . . . . . . . . . . . . . . . . . . . . .382 21.13 RAM Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382 21.14 EEPROM Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . .382 21.15 BDLC Transmitter VPW Symbol Timings . . . . . . . . . . . . . . . .382 21.16 BDLC Receiver VPW Symbol Timings . . . . . . . . . . . . . . . . . .383 21.17 BDLC Transmitter DC Electrical Characteristics . . . . . . . . . .384 21.18 BDLC Receiver DC Electrical Characteristics . . . . . . . . . . . .384
Section 22. Mechanical Data
22.1 22.2 22.3 22.4
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Table of Contents
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 52-Pin Plastic Leaded Chip Carrier Package (Case 778). . . .386 64-Pin Quad Flat Pack (Case 840B) . . . . . . . . . . . . . . . . . . .387
Advance Information 17
NON-DISCLOSURE
AGREEMENT
REQUIRED
Table of Contents REQUIRED Section 23. Ordering Information
23.1 23.2 23.3 23.4 23.5 23.6 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389 MCU Ordering Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389 Application Program Media. . . . . . . . . . . . . . . . . . . . . . . . . . .390 ROM Program Verification . . . . . . . . . . . . . . . . . . . . . . . . . . .391 MC Order Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
NON-DISCLOSURE
Advance Information 18 Table of Contents
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
List of Figures
Figure 1-1 1-2 1-3 1-4 2-1 2-2 5-1 6-1 6-2 6-3 7-1 7-2 7-3 7-4 7-5 7-6 8-1 8-2 8-3 8-4 8-5
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Title
Page
Memory Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Control, Status, and Data Register. . . . . . . . . . . . . . . . . . . .47 Mask Option Register (MOR) . . . . . . . . . . . . . . . . . . . . . . . .60 EEPROM Control Register (EECR) . . . . . . . . . . . . . . . . . . .70 EEPROM Array Control Register (EEACR) . . . . . . . . . . . . .72 EEPROM Non-volatile Register (EENVR) . . . . . . . . . . . . . .72 CPU Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Accumulator (A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Index Register (H:X). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Stack Pointer (SP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Program Counter (PC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Condition Code Register (CCR) . . . . . . . . . . . . . . . . . . . . . .81 CGM Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 CGM External Connections . . . . . . . . . . . . . . . . . . . . . . . .105 PLL Control Register (PCTL) . . . . . . . . . . . . . . . . . . . . . . .108 PLL Bandwidth Control Register (PBWC) . . . . . . . . . . . . .110 PLL Programming Register (PPG) . . . . . . . . . . . . . . . . . . .112
Advance Information List of Figures 19
NON-DISCLOSURE
AGREEMENT
MCU Block Diagram for 52-Pin PLCC and 64-Pin QFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 52-Pin PLCC Assignments (Top View) . . . . . . . . . . . . . . . .33 64-Pin QFP Assignments (Top View). . . . . . . . . . . . . . . . . .34 Power Supply Bypassing . . . . . . . . . . . . . . . . . . . . . . . . . . .35
REQUIRED
List of Figures REQUIRED
Figure 9-1 9-2 9-3 9-4 9-5 9-6 9-7 9-8 9-9 9-10 9-11 9-12 9-13 9-14 9-15 9-16 9-17 9-18 10-1 10-2 11-1 11-2 11-3 11-4 12-1 12-2 12-3 12-4 12-5 Title Page
SIM Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 CGM Clock Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 External Reset Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Internal Reset Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Sources of Internal Reset. . . . . . . . . . . . . . . . . . . . . . . . . .128 POR Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 Hardware Interrupt Entry . . . . . . . . . . . . . . . . . . . . . . . . . .132 Interrupt Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Hardware Interrupt Recovery . . . . . . . . . . . . . . . . . . . . . . .134 Interrupt Recognition Example . . . . . . . . . . . . . . . . . . . . . .135 Wait Mode Entry Timing . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Wait Recovery from Interrupt or Break . . . . . . . . . . . . . . . .138 Wait Recovery from Internal Reset . . . . . . . . . . . . . . . . . .138 Stop Mode Entry Timing. . . . . . . . . . . . . . . . . . . . . . . . . . .139 Stop Mode Recovery from Interrupt or Break. . . . . . . . . . .139 SIM Break Status Register (SBSR) . . . . . . . . . . . . . . . . . .140 SIM Reset Status Register (SRSR) . . . . . . . . . . . . . . . . . .142 SIM Break Flag Control Register (SBFCR) . . . . . . . . . . . .143 LVI Module Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . .147 LVI Status Register (LVISR). . . . . . . . . . . . . . . . . . . . . . . .148 Break Module Block Diagram. . . . . . . . . . . . . . . . . . . . . . .153 Break Status and Control Register (BRKSCR) . . . . . . . . .155 Break Address Register (BRKH) . . . . . . . . . . . . . . . . . . . .156 Break Address Register (BRKL). . . . . . . . . . . . . . . . . . . . .156 Monitor Mode Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161 Monitor Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 Sample Monitor Waveforms . . . . . . . . . . . . . . . . . . . . . . . .163 Read Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Break Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
NON-DISCLOSURE
Advance Information 20
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 List of Figures MOTOROLA
List of Figures
Figure 13-1 13-2 14-1 14-2 14-3 15-1 15-2 15-3 15-4 15-5 15-6 15-7 15-8 15-9 15-10 15-11 15-12 15-13 15-14 15-15 15-16 15-17 15-18 16-1 16-2 16-3 16-4 16-5 16-6
Title
Page
COP Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170 COP Control Register (COPCTL). . . . . . . . . . . . . . . . . . . .173 IRQ Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 IRQ Interrupt Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . .178 IRQ Status and Control Register (ISCR) . . . . . . . . . . . . . .181 Port A Data Register (PTA) . . . . . . . . . . . . . . . . . . . . . . . .185 Data Direction Register A (DDRA) . . . . . . . . . . . . . . . . . . .186 Port A I/O Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186 Port B Data Register (PTB) . . . . . . . . . . . . . . . . . . . . . . . .188 Data Direction Register B (DDRB) . . . . . . . . . . . . . . . . . . .189 Port B I/O Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 Port C Data Register (PTC) . . . . . . . . . . . . . . . . . . . . . . . .191 Data Direction Register C (DDRC) . . . . . . . . . . . . . . . . . . .192 Port C I/O Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193 Port D Data Register (PTD) . . . . . . . . . . . . . . . . . . . . . . . .194 Data Direction Register D (DDRD) . . . . . . . . . . . . . . . . . . .195 Port D I/O Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Port E Data Register (PTE) . . . . . . . . . . . . . . . . . . . . . . . .197 Data Direction Register E (DDRE) . . . . . . . . . . . . . . . . . . .199 Port E I/O Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 Data Direction Register F (DDRF) . . . . . . . . . . . . . . . . . . .201 Data Direction Register F (DDRF) . . . . . . . . . . . . . . . . . . .202 Port F I/O Circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 TIM Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207 PWM Period and Pulse Width . . . . . . . . . . . . . . . . . . . . . .213 TIM Status and Control Register (TSC) . . . . . . . . . . . . . . .222 TIM Counter Registers (TCNTH and TCNTL) . . . . . . . . . .224 TIM Counter Modulo Registers (TMODH and TMODL) . . .225 TIM Channel Status and Control Registers (TSC0-TSC5) . . . . . . . . . . . . . .226
Advance Information List of Figures 21
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
NON-DISCLOSURE
AGREEMENT
REQUIRED
List of Figures REQUIRED
Figure 16-7 16-8 17-1 17-2 17-3 17-4 17-5 17-6 17-7 17-8 17-9 17-10 17-11 17-12 17-13 18-1 18-2 18-3 18-4 18-5 18-6 18-7 18-8 18-9 18-10 18-11 18-12 18-13 18-14 19-1 19-2
Advance Information 22 List of Figures
Title
Page
CHxMAX Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231 TIM Channel Registers (TCH0H/L-TCH3H/L) . . . . . . . . . .232 SCI Module Block Diagram . . . . . . . . . . . . . . . . . . . . . . . .238 SCI Data Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 SCI Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242 SCI Receiver Block Diagram . . . . . . . . . . . . . . . . . . . . . . .247 Receiver Data Sampling. . . . . . . . . . . . . . . . . . . . . . . . . . .250 SCI Control Register 1 (SCC1) . . . . . . . . . . . . . . . . . . . . .258 SCI Control Register 2 (SCC2) . . . . . . . . . . . . . . . . . . . . .261 SCI Control Register 3 (SCC3) . . . . . . . . . . . . . . . . . . . . .264 SCI Status Register 1 (SCS1) . . . . . . . . . . . . . . . . . . . . . .265 Flag Clearing Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . .268 SCI Status Register 2 (SCS2) . . . . . . . . . . . . . . . . . . . . . .269 SCI Data Register (SCDR). . . . . . . . . . . . . . . . . . . . . . . . .270 SCI BAUD Rate Register 1 (SCBR) . . . . . . . . . . . . . . . . . .271 SPI Module Block Diagram . . . . . . . . . . . . . . . . . . . . . . . .279 Full-Duplex Master-Slave Connections . . . . . . . . . . . . . . .280 Transmission Format (CPHA = 0) . . . . . . . . . . . . . . . . . . .283 CPHA/SS Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284 Transmission Format (CPHA = 1) . . . . . . . . . . . . . . . . . . .285 Transmission Start Delay (Master) . . . . . . . . . . . . . . . . . . .287 Missed Read of Overflow Condition . . . . . . . . . . . . . . . . . .289 Clearing SPRF When OVRF Interrupt Is Not Enabled . . . .290 SPI Interrupt Request Generation . . . . . . . . . . . . . . . . . . .293 SPRF/SPTE CPU Interrupt Timing. . . . . . . . . . . . . . . . . . .294 CPHA/SS Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 SPI Control Register (SPCR) . . . . . . . . . . . . . . . . . . . . . . .302 SPI Status and Control Register (SPSCR). . . . . . . . . . . . .305 SPI Data Register (SPDR) . . . . . . . . . . . . . . . . . . . . . . . . .308 ADC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311 ADC Status and Control Register (ADSCR). . . . . . . . . . . .315
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
NON-DISCLOSURE
AGREEMENT
List of Figures
Figure 19-3 19-4 20-1 20-2 20-3 20-4 20-5 20-6 20-7 20-8 20-9 20-10 20-11 20-12 20-13 20-14 20-15 20-16 20-17 20-18 20-19 20-20 21-1 21-2 21-3
Title
Page
ADC Data Register (ADR) . . . . . . . . . . . . . . . . . . . . . . . . .318 ADC Input Clock Register (ADICLK) . . . . . . . . . . . . . . . . .318 BDLC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324 BDLC Operating Modes State Diagram . . . . . . . . . . . . . . .326 BDLC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329 BDLC Rx Digital Filter Block Diagram . . . . . . . . . . . . . . . .330 J1850 Bus Message Format (VPW). . . . . . . . . . . . . . . . . .332 J1850 VPW Symbols with Nominal Symbol Times . . . . . .336 J1850 VPW Received Passive Symbol Times . . . . . . . . . .339 J1850 VPW Received Passive EOF and IFS Symbol Times . . . . . . . . . . . . . . . . . . . . .340 J1850 VPW Received Active Symbol Times . . . . . . . . . . .341 J1850 VPW Received BREAK Symbol Times . . . . . . . . . .342 J1850 VPW Bitwise Arbitrations. . . . . . . . . . . . . . . . . . . . .343 BDLC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345 BDLC Protocol Handler Outline . . . . . . . . . . . . . . . . . . . . .346 BDLC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352 BDLC Analog and Roundtrip Delay Register (BARD) . . . .353 BDLC Control Register 1 (BCR1) . . . . . . . . . . . . . . . . . . . .354 BDLC Control Register 2 (BCR2) . . . . . . . . . . . . . . . . . . . .357 Types of In-Frame Response (IFR) . . . . . . . . . . . . . . . . . .360 BDLC State Vector Register (BSVR) . . . . . . . . . . . . . . . . .364 BDLC Data Register (BDR) . . . . . . . . . . . . . . . . . . . . . . . .366 SPI Master Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378 SPI Slave Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379 BDLC Variable Pulse Width Modulation (VPW) Symbol Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383
MC68HC08AS32 -- Rev. 3.0 MOTOROLA List of Figures
Advance Information 23
NON-DISCLOSURE
AGREEMENT
REQUIRED
List of Figures REQUIRED NON-DISCLOSURE
Advance Information 24 List of Figures
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
List of Tables
Table 1-1 1-2 2-1 6-1 6-2 6-3 7-1 7-2 8-1 8-2 8-3 9-1 9-2 9-3 10-1 10-2 11-1 12-1 12-2 12-3 12-4 12-5
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Title
Page
Vector Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 EEPROM Program/Erase Cycling Reduction. . . . . . . . . . . . .67 EEPROM Array Address Blocks. . . . . . . . . . . . . . . . . . . . . . .68 EEPROM Program/Erase Mode Select . . . . . . . . . . . . . . . . .71 Instruction Set Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Opcode Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 CGM I/O Register Summary. . . . . . . . . . . . . . . . . . . . . . . . . .97 CGM I/O Register Summary. . . . . . . . . . . . . . . . . . . . . . . . .107 VCO Frequency Multiplier (N) Selection. . . . . . . . . . . . . . . .112 SIM I/O Register Summary. . . . . . . . . . . . . . . . . . . . . . . . . .123 Signal Name Conventions . . . . . . . . . . . . . . . . . . . . . . . . . .124 PIN Bit Set Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 LVI I/O Register Summary . . . . . . . . . . . . . . . . . . . . . . . . . .147 LVIOUT Bit Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 Break I/O Register Summary . . . . . . . . . . . . . . . . . . . . . . . .153 Mode Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Mode Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 READ (Read Memory) Command . . . . . . . . . . . . . . . . . . . .165 WRITE (Write Memory) Command. . . . . . . . . . . . . . . . . . . .166 IREAD (Indexed Read) Command . . . . . . . . . . . . . . . . . . . .166
Advance Information List of Tables 25
NON-DISCLOSURE
AGREEMENT
External Pins Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Clock Source Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
REQUIRED
List of Tables REQUIRED
Table 12-6 12-7 12-8 12-9 14-1 15-1 15-2 15-3 15-4 15-5 15-6 15-7 16-1 16-2 16-3 17-1 17-2 17-3 17-4 17-5 17-6 17-7 17-8 17-9 17-10 18-1 18-2 18-3 18-4 18-5 18-6 Title Page
IWRITE (Indexed Write) Command . . . . . . . . . . . . . . . . . . .167 READSP (Read Stack Pointer) Command. . . . . . . . . . . . . .167 RUN (Run User Program) Command. . . . . . . . . . . . . . . . . .168 Monitor Baud Rate Selection . . . . . . . . . . . . . . . . . . . . . . . .168 IRQ I/O Register Summary. . . . . . . . . . . . . . . . . . . . . . . . . .177 I/O Port Register Summary . . . . . . . . . . . . . . . . . . . . . . . . .184 Port A Pin Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187 Port B Pin Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190 Port C Pin Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193 Port D Pin Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Port E Pin Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200 Port F Pin Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 TIM I/O Register Summary. . . . . . . . . . . . . . . . . . . . . . . . . .208 Prescaler Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Mode, Edge, and Level Selection. . . . . . . . . . . . . . . . . . . . .230 SCI I/O Register Summary . . . . . . . . . . . . . . . . . . . . . . . . . .239 SCI Transmitter I/O Register Summary . . . . . . . . . . . . . . . .243 SCI Receiver I/O Register Summary . . . . . . . . . . . . . . . . . .248 Start Bit Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Data Bit Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Stop Bit Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 Character Format Selection . . . . . . . . . . . . . . . . . . . . . . . . .260 SCI Baud Rate Prescaling . . . . . . . . . . . . . . . . . . . . . . . . . .271 SCI Baud Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . .272 SCI Baud Rate Selection Examples . . . . . . . . . . . . . . . . . . .273 Pin Name Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 I/O Register Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 SPI I/O Register Summary . . . . . . . . . . . . . . . . . . . . . . . . . .278 SPI Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292 SPI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 SPI Master Baud Rate Selection . . . . . . . . . . . . . . . . . . . . .307
NON-DISCLOSURE
Advance Information 26
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 List of Tables MOTOROLA
List of Tables
Table 19-1 19-2 20-1 20-2 20-3 20-4 20-5 20-6 23-1
Title
Page
Mux Channel Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317 ADC Clock Divide Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . .319 BDLC I/O Register Summary . . . . . . . . . . . . . . . . . . . . . . . .325 BDLC J1850 Bus Error Summary. . . . . . . . . . . . . . . . . . . . .351 BDLC Transceiver Delay . . . . . . . . . . . . . . . . . . . . . . . . . . .354 BDLC Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356 BDLC Transmit In-Frame Response Control Bit Priority Encoding . . . . . . . . . . . . . . . . . . . . . .359 BDLC Interrupt Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 MC Order Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
MC68HC08AS32 -- Rev. 3.0 MOTOROLA List of Tables
Advance Information 27
NON-DISCLOSURE
AGREEMENT
REQUIRED
List of Tables REQUIRED NON-DISCLOSURE
Advance Information 28 List of Tables
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 1. General Description
1.1 Contents
1.2 1.3 1.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 MCU Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 29
NON-DISCLOSURE
1.5 Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 1.5.1 Power Supply Pins (VDD and VSS) . . . . . . . . . . . . . . . . . . .35 1.5.2 Oscillator Pins (OSC1 and OSC2) . . . . . . . . . . . . . . . . . . .36 1.5.3 External Reset Pin (RST) . . . . . . . . . . . . . . . . . . . . . . . . . .36 1.5.4 External Interrupt Pin (IRQ). . . . . . . . . . . . . . . . . . . . . . . . .36 1.5.5 Analog Power Supply Pin (VDDA/VDDAREF). . . . . . . . . . . . .36 1.5.6 ADC High Reference Pin (VREFH) . . . . . . . . . . . . . . . . . . . .36 1.5.7 Analog Ground Pin (VSSA/VREFL) . . . . . . . . . . . . . . . . . . . .37 1.5.8 External Filter Capacitor Pin (CGMXFC). . . . . . . . . . . . . . .37 1.5.9 Port A Input/Output (I/O) Pins (PTA7-PTA0) . . . . . . . . . . .37 1.5.10 Port B I/O Pins (PTB7/ATD7-PTB0/ATD0). . . . . . . . . . . . .37 1.5.11 Port C I/O Pins (PTC4-PTC0). . . . . . . . . . . . . . . . . . . . . . .37 1.5.12 Port D I/O Pins (PTD6/ATD14/TCLKA-PTD0/ATD8) . . . . .38 1.5.13 Port E I/O Pins (PTE7/SPSCK-PTE0/TxD) . . . . . . . . . . . .38 1.5.14 Port F I/O Pins (PTF3/TCH5-PTF0/TCH2) . . . . . . . . . . . . .38 1.5.15 J1850 Transmit Pin Digital (BDTxD) . . . . . . . . . . . . . . . . . .38 1.5.16 J1850 Receive Pin Digital (BDRxD) . . . . . . . . . . . . . . . . . .38
AGREEMENT
REQUIRED
General Description REQUIRED 1.2 Introduction
The MC68HC08AS32 is a member of the low-cost, high-performance M68HC08 Family of 8-bit microcontroller units (MCUs). The M68HC08 Family is based on the customer-specified integrated circuit (CSIC) design strategy. All MCUs in the family use the enhanced M68HC08 central processor unit (CPU08) and are available with a variety of modules, memory sizes and types, and package types.
AGREEMENT
1.3 Features
Features of the MC68HC08AS32 include: * * * * * * * * * * * * * High-performance M68HC08 architecture Fully upward-compatible object code with M6805, M146805, and M68HC05 Families 8.4-MHz internal bus frequency 32,256 bytes of read-only memory (ROM) ROM data security 512 bytes of on-chip electrically erasable programmable read-only memory (EEPROM) 1024 bytes of on-chip random-access memory (RAM) Serial peripheral interface module (SPI) Serial communications interface module (SCI) 16-bit, 6-channel timer interface module (TIM) Clock generator module (CGM) 8-bit, 15-channel analog-to-digital converter module (ADC) SAE J1850 byte data link controller digital module (BDLC-D)
NON-DISCLOSURE
Advance Information 30
MC68HC08AS32 -- Rev. 3.0 General Description MOTOROLA
General Description MCU Block Diagram
*
System protection features: - Computer operating properly (COP) with optional reset - Low-voltage detection with optional reset - Illegal opcode detection with optional reset - Illegal address detection with optional reset
* *
Low-power design (fully static with stop and wait modes) Master reset pin and power-on reset
* * * * * * * * * *
Enhanced HC05 programming model Extensive loop control functions 16 addressing modes (eight more than the HC05) 16-bit index register and stack pointer Memory-to-memory data transfers Fast 8 x 8 multiply instruction Fast 16/8 divide instruction Binary-coded decimal (BCD) instructions
C language support
1.4 MCU Block Diagram
Figure 1-1 shows the structure of the MC68HC08AS32.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 31
NON-DISCLOSURE
Optimization for controller applications
AGREEMENT
Features of the CPU08 include:
REQUIRED
NON-DISCLOSURE
32 General Description MC68HC08AS32 -- Rev. 3.0 MOTOROLA Advance Information
AGREEMENT
REQUIRED General Description
DDRA
INTERNAL BUS M68HC08 CPU CPU REGISTERS ARITHMETIC/LOGIC UNIT VREFH ANALOG-TO-DIGITAL CONVERTER MODULE
PTA
PTA7-PTA0
DDRB
PTB
PTB7/ATD7-PTB0/ATD0
CONTROL AND STATUS REGISTERS -- 69 BYTES
DDRC
USER ROM -- 32,256 BYTES LOW-VOLTAGE INHIBIT MODULE USER EEPROM -- 512 BYTES DDRD COMPUTER OPERATING PROPERLY MODULE PTD
PTC
BREAK MODULE
PTC4-PTC3 PTC2/MCLK PTC1-PTC0
PTD6/ATD14/TCLK PTD5/ATD13-PTD0/ATD8
USER RAM -- 1024 BYTES
MONITOR ROM -- 224 BYTES
TIMER INTERFACE MODULE
USER ROM VECTOR SPACE -- 36 BYTES DDRE SERIAL COMMUNICATIONS INTERFACE MODULE PTE
OSC1 OSC2 CGMXFC
CLOCK GENERATOR MODULE
SERIAL PERIPHERAL INTERFACE MODULE PTF RST DDRF SYSTEM INTEGRATION MODULE BYTE DATA LINK CONTROLLER DIGITAL MODULE IRQ IRQ MODULE BDRxD BDTxD
PTE7/SPSCK PTE6/MOSI PTE5/MISO PTE4/SS PTE3/TCH1 PTE2/TCH0 PTE1/RxD PTE0/TxD PTF3/TCH5 PTF2/TCH4 PTF1/TCH3 PTF0/TCH2
POWER-ON RESET MODULE VSS VDD VDDA/VDDAREF VSSA/VREFL
POWER
Figure 1-1. MCU Block Diagram for 52-Pin PLCC and 64-Pin QFP
General Description Pin Assignments
1.5 Pin Assignments
Figure 1-2 shows the 52-pin plastic leaded chip carrier (PLCC) assignments.
PTD6/ATD14/TCLK
VDDA/VDDAREF
PTD5/ATD13
1
47
PTD4/ATD12
PTC2/MCLK
VSSA/VREFL
CGMXFC
VREFH
OSC1
OSC2
PTC3
PTC1
PTC0
PTC4 IRQ RST PTF0/TCH2 PTF1/TCH3 PTF2/TCH4 PTF3/TCH5 BDRxD BDTxD PTE0/TxD PTE1/RxD PTE2/TCH0 PTE3/TCH1
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
46 45 44 43 42 41 40 39 38 37 36 35 34
PTD3/ATD11 PTD2/ATD10 PTD1/ATD9 PTD0/ATD8 PTB7/ATD7 PTB6/ATD6 PTB5/ATD5 PTB4/ATD4 PTB3/ATD3 PTB2/ATD2 PTB1/ATD1 PTB0/ATD0 PTA7
Figure 1-2. 52-Pin PLCC Assignments (Top View)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 33
NON-DISCLOSURE
30
31
32
PTE7/SPSCK
PTE5/MISO
PTE6/MOSI
VSS
PTA0
PTA1
PTA2
PTA3
PTA4
PTA5
PTE4/SS
PTA6
VDD
33
AGREEMENT
7
6
5
4
3
2
52
51
50
49
48
REQUIRED
General Description REQUIRED
Figure 1-3 shows the 64-pin quad flat pack (QFP) assignments.
PTD6/ATD14/TCLK
PTD5 /ATD13
PTC2/MCLK
CGMXFC
VREFH
OSC1
OSC2
PTC3
PTC1
PTC0
VDDA
VSSA
NC
NC
PTD4/ ATD12 50
64
63
62
61
60
59
58
57
56
55
54
53
52
PTC4
51
49
NC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
48 47 46 45 44 43 42 41 40 39 38 37 36 35 34
NC PTD3/ATD11 PTD2/ATD10 NC NC PTD1/ATD9 PTD0/ATD8 PTB7/ATD7 PTB6/ATD6 PTB5/ATD5 PTB4/ATD4 PTB3/ATD3 PTB2/ATD2 PTB1/ATD1 PTB0/ATD0
AGREEMENT
IRQ RST PTF0/TCH2 PTF1/TCH3 PTF2/TCH4 PTF3/TCH5 NC BDRxD BDTxD NC NC
NON-DISCLOSURE
PTE0/TxD PTE1/RxD PTE2/TCH0 PTE3/TCH1 16
18
19
20
21
22
23
24
25
26
27
28
29
30
PTE4/SS 17
31
33 PTA6 32
PTA7
PTE7/SPSCK
NC
NC
PTE5/MISO
PTE6/MOSI
VDD
NC
PTA0
PTA1
PTA2
PTA3
PTA4
Figure 1-3. 64-Pin QFP Assignments (Top View)
Advance Information 34 General Description
PTA5
VSS
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
General Description Pin Assignments
1.5.1 Power Supply Pins (VDD and VSS) VDD and VSS are the power supply and ground pins. The MCU operates from a single power supply. Fast signal transitions on MCU pins place high, short-duration current demands on the power supply. To prevent noise problems, take special care to provide power supply bypassing at the MCU as Figure 1-4 shows. Place the C1 bypass capacitor as close to the MCU as possible. Use a high-frequency-response ceramic capacitor for C1. C2 is an optional bulk current bypass capacitor for use in applications that require the port pins to source high current levels.
MCU
VDD VSS
C1 0.1 F + C2
VDD
NOTE: Component values shown represent typical applications.
Figure 1-4. Power Supply Bypassing VSS is also the ground for the port output buffers and the ground return for the serial clock in the serial peripheral interface module (SPI). (See Section 18. Serial Peripheral Interface (SPI).)
NOTE:
VSS must be grounded for proper MCU operation.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 35
NON-DISCLOSURE
AGREEMENT
REQUIRED
General Description REQUIRED
1.5.2 Oscillator Pins (OSC1 and OSC2) The OSC1 and OSC2 pins are the connections for the on-chip oscillator circuit. (See Section 8. Clock Generator Module (CGM).)
1.5.3 External Reset Pin (RST) A logic 0 on the RST pin forces the MCU to a known startup state. RST is bidirectional, allowing a reset of the entire system. It is driven low when any internal reset source is asserted. (See Section 9. System Integration Module (SIM) for more information.)
AGREEMENT
1.5.4 External Interrupt Pin (IRQ) IRQ is an asynchronous external interrupt pin. (See Section 14. External Interrupt (IRQ).)
1.5.5 Analog Power Supply Pin (VDDA/VDDAREF) VDDA/VDDAREF is the power supply pin for the analog portion of the chip. These modules are the analog-to-digital converter (ADC) and the clock generator module (CGM). (See Section 8. Clock Generator Module (CGM) and Section 19. Analog-to-Digital Converter (ADC).)
NON-DISCLOSURE
1.5.6 ADC High Reference Pin (VREFH) VREFH is the high reference voltage for all analog-to-digital conversions. (See Section 19. Analog-to-Digital Converter (ADC).)
Advance Information 36 General Description
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
General Description Pin Assignments
1.5.7 Analog Ground Pin (VSSA/VREFL) The VSSA/VREFL analog ground pin is used only for the ground connections for the analog sections of the circuit and should be decoupled as per the VSS digital ground pin. The analog sections consist of a clock generator module (CGM) and an analog-to-digital converter (ADC). VSSA/VREFL is also the lower reference supply for the ADC. (See Section 8. Clock Generator Module (CGM) and Section 19. Analogto-Digital Converter (ADC).)
1.5.8 External Filter Capacitor Pin (CGMXFC) CGMXFC is an external filter capacitor connection for the CGM. (See Section 8. Clock Generator Module (CGM).)
1.5.9 Port A Input/Output (I/O) Pins (PTA7-PTA0) PTA7-PTA0 are general-purpose bidirectional I/O port pins. (See Section 15. Input/Output (I/O) Ports.)
1.5.10 Port B I/O Pins (PTB7/ATD7-PTB0/ATD0) Port B is an 8-bit special function port that shares all eight pins with the analog-to-digital converter (ADC). (See Section 19. Analog-to-Digital Converter (ADC) and Section 15. Input/Output (I/O) Ports.)
1.5.11 Port C I/O Pins (PTC4-PTC0) PTC4-PTC3 and PTC1-PTC0 are general-purpose bidirectional I/O port pins. PTC2/MCLK is a special function port that shares its pin with the system clock. (See Section 15. Input/Output (I/O) Ports.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 37
NON-DISCLOSURE
AGREEMENT
REQUIRED
General Description REQUIRED
1.5.12 Port D I/O Pins (PTD6/ATD14/TCLKA-PTD0/ATD8) Port D is a 7-bit special function port that shares all of its pins with the analog-to-digital converter module (ADC) and one of its pins with the timer interface module (TIM). (See Section 16. Timer Interface (TIM), Section 19. Analog-to-Digital Converter (ADC), and Section 15. Input/Output (I/O) Ports.)
1.5.13 Port E I/O Pins (PTE7/SPSCK-PTE0/TxD)
AGREEMENT
Port E is an 8-bit special function port that shares two of its pins with the timer interface module (TIM), four of its pins with the serial peripheral interface module (SPI), and two of its pins with the serial communication interface module (SCI). (See Section 17. Serial Communications Interface (SCI), Section 18. Serial Peripheral Interface (SPI), Section 16. Timer Interface (TIM), and Section 15. Input/Output (I/O) Ports.)
1.5.14 Port F I/O Pins (PTF3/TCH5-PTF0/TCH2) Port F is a 4-bit special function port that shares all of its pins with the timer interface module (TIM). (See Section 16. Timer Interface (TIM) and Section 15. Input/Output (I/O) Ports.)
NON-DISCLOSURE
1.5.15 J1850 Transmit Pin Digital (BDTxD) BDTxD is a serial digital output data physical interface to the J1850. (See Section 20. Byte Data Link Controller-Digital (BDLC-D).)
1.5.16 J1850 Receive Pin Digital (BDRxD) BDRxD is a serial digital input data physical interface from the J1850. (See Section 20. Byte Data Link Controller-Digital (BDLC-D).)
Advance Information 38 General Description
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
General Description Pin Assignments
Table 1-1. External Pins Summary
Pin Name PTA7-PTA0 PTB7/ATD7- PTB0/ATD0 PTC4-PTC3 PTC2/MCLK PTC1-PTC0 PTD6/ATD14/TCLK PTD5/ATD13- PTD0/ATD8 PTE7/SPSCK PTE6/MOSI PTE5/MISO PTE4/SS PTE3/TCH1 PTE2/TCH0 PTE1/RxD PTE0/TxD PTF3/TCH5 PTF2/TCH4 PTF1/TCH3 Function General-Purpose I/O General-Purpose I/O ADC Channel General-Purpose I/O General-Purpose I/O, Bus Clock Output General-Purpose I/O General-Purpose I/O ADC Channel/Timer External Input Clock General-Purpose/O ADC Channel General-Purpose I/O SPI Clock General-Purpose I/O SPI Data Path General-Purpose I/O SPI Data Path General-Purpose I/O SPI Slave Select General-Purpose I/O Timer Channel 1 General-Purpose I/O Timer Channel 0 General-Purpose I/O SCI Receive Data General-Purpose I/O SCI Transmit Data General-Purpose I/O Timer Channel 5 General-Purpose I/O Timer Channel 4 General-Purpose I/O Timer Channel 3 Driver Type Dual State Dual State Dual State Dual State Dual State Dual State Hysteresis No No No No No No Reset State Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z
Dual State Dual State Open Drain Dual State Open Drain Dual State Open Drain Dual State Dual State Dual State Dual State Dual State Dual State Dual State Dual State
No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z Input, Hi-Z
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 39
NON-DISCLOSURE
AGREEMENT
REQUIRED
General Description REQUIRED
Table 1-1. External Pins Summary (Continued)
Pin Name PTF0/TCH2 VDD VSS VDDA/VDDAREF VSSA/VREFL VREFH OSC1 OSC2 CGMXFC IRQ RST BDRxD BDTxD Function General-Purpose I/O Timer Channel 2 Chip Power Supply Chip Ground Analog Power Supply (CGM and ADC) Analog Ground A/D Reference Voltage A/D Reference Voltage External Clock In External Clock Out PLL Loop Filter Cap External Interrupt Request Reset BDLC-D Serial Input BDLC-D Serial Output Driver Type Dual State N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Output Hysteresis Yes N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A No No Reset State Input, Hi-Z N/A N/A N/A N/A N/A Input, Hi-Z Output N/A Input, Hi-Z Output Low Input, Hi-Z Output Low
NON-DISCLOSURE
Advance Information 40 General Description
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
General Description Pin Assignments
Table 1-2. Clock Source Summary
Module ADC BDLC COP CPU EEPROM SPI SCI TIM SIM IRQ BRK LVI CGM Clock Source CGMXCLK or Bus Clock CGMXCLK CGMXCLK Bus Clock Internal RC Oscillator or Bus Clock Bus Clock/SPSCK CGMXCLK Bus Clock or PTD6/ATD14/TCLK CGMOUT and CGMXCLK Bus Clock Bus Clock Bus Clock OSC1 and OSC2
MC68HC08AS32 -- Rev. 3.0 MOTOROLA General Description
Advance Information 41
NON-DISCLOSURE
AGREEMENT
REQUIRED
General Description REQUIRED NON-DISCLOSURE
Advance Information 42 General Description
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 2. Memory Map
2.1 Contents
2.2 2.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Input/Output (I/O) Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
2.2 Introduction
The CPU08 can address 64 Kbytes of memory space. The memory map, shown in Figure 2-1, includes: * * * * * 32,256 bytes of user ROM 1024 bytes of RAM 512 bytes of EEPROM 36 bytes of user-defined vectors 224 bytes of monitor ROM
These definitions apply to the memory map representation of reserved and unimplemented locations. * * Reserved -- Accessing a reserved location can have unpredictable effects on MCU operation. Unimplemented -- Accessing an unimplemented location causes an illegal address reset if illegal address resets are enabled.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Memory Map
Advance Information 43
NON-DISCLOSURE
AGREEMENT
REQUIRED
Memory Map REQUIRED
$0000 $003F $0040 $004F $0050
I/O REGISTERS -- 58 BYTES ($000A, $000B, $000E, $000F, $001B, AND $0021 ARE RESERVED)
UNIMPLEMENTED -- 16 BYTES
AGREEMENT
$044F $0450 $07FF $0800 $09FF $0A00
RAM -- 1024 BYTES
RESERVED -- 2 BYTES UNIMPLEMENTED -- 942BYTES
EEPROM -- 512 BYTES
RESERVED -- 2 BYTES UNIMPLEMENTED -- 30,206 BYTES
NON-DISCLOSURE
$7FFF $8000 $FDFF $FE00 $FE01 $FE02 $FE03 $FE04 $FE05 $FE06 $FE07 SIM BREAK STATUS REGISTER (SBSR) SIM RESET STATUS REGISTER (SRSR) RESERVED SIM BREAK FLAG CONTROL REGISTER (SBFCR) RESERVED RESERVED RESERVED RESERVED ROM -- 32,256 BYTES
Figure 2-1. Memory Map
Advance Information 44 Memory Map
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Memory Map Introduction
$FE08 $FE09 $FE0A $FE0B $FE0C $FE0D $FE0E $FE0F $FE10 $FE1B $FE1C $FE1D $FE1E $FE1F $FE20 $FEFF $FF00 $FFDB $FFDC $FFFF
RESERVED RESERVED RESERVED RESERVED BREAK ADDRESS REGISTER HIGH (BRKH) BREAK ADDRESS REGISTER LOW (BRKL) BREAK STATUS AND CONTROL REGISTER (BRKSCR) LVI STATUS REGISTER (LVISR)
RESERVED -- 12 BYTES
EEPROM NON-VOLATILE REGISTER (EENVR) EEPROM CONTROL REGISTER (EECR) RESERVED EEPROM ARRAY CONFIGURATION REGISTER (EEACR)
MONITOR ROM -- 224 BYTES
UNIMPLEMENTED -- 220 BYTES
INTERRUPT AND RESET VECTORS -- 36 BYTES
Figure 2-1. Memory Map (Continued)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Memory Map
Advance Information 45
NON-DISCLOSURE
AGREEMENT
REQUIRED
Memory Map REQUIRED 2.3 Input/Output (I/O) Section
Addresses $0000-$003F, shown in Figure 2-2, contain most of the control, status, and data registers. Additional I/O registers have these addresses: * * * $FE00, SIM break status register, SBSR $FE01, SIM reset status register, SRSR $FE03, SIM break flag control register, SBFCR $FE0C and $FE0D, break address registers, BRKH and BRKL $FE0E, break status and control register, BRKSCR $FE0F, LVI status register, LVISR $FE1C, EEPROM non-volatile register, EENVR $FE1D, EEPROM control register, EECR $FE1F, EEPROM array configuration register, EEACR $FFFF, COP control register, COPCTL
AGREEMENT
* * * * * * *
Table 2-1 is a list of vector locations.
NON-DISCLOSURE
Advance Information 46 Memory Map
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Memory Map Input/Output (I/O) Section
Addr. $0000
Register Name Port A Data Register Read: (PTA) Write: Port B Data Register Read: (PTB) Write: Port C Data Register Read: (PTC) Write: Port D Data Register Read: (PTD) Write:
Bit 7 PTA7
6 PTA6
5 PTA5
4 PTA4
3 PTA3
2 PTA2
1 PTA1
Bit 0 PTA0
$0001
PTB7 0 R 0 R
PTB6 0 R PTD6
PTB5 0 R PTD5
PTB4
PTB3
PTB2
PTB1
PTB0
$0002
PTC4
PTC3
PTC2
PTC1
PTC0
$0004
Data Direction Register A Read: DDRA7 (DDRA) Write: Data Direction Register B Read: DDRB7 (DDRB) Write: Data Direction Register C Read: MCLKEN (DDRC) Write: Data Direction Register D Read: (DDRD) Write: Port E Data Register Read: (PTE) Write: Port F Data Register Read: (PTF) Write: Reserved Read: Write: Read: Write: 0 R PTE7 0 R R
DDRA6
DDRA5
DDRA4
DDRA3
DDRA2
DDRA1
DDRA0
$0005
DDRB6 0 R DDRD6
DDRB5 0 R DDRD5
DDRB4
DDRB3
DDRB2
DDRB1
DDRB0
$0006
DDRC4
DDRC3
DDRC2
DDRC1
DDRC0
$0007
DDRD4
DDRD3
DDR2
DDRD1
DDRD0
$0009
0 R R
0 R R
0 R R
PTF3
PTF2
PTF1
PTF0
$000A
R
R
R
R
$000B
Reserved
R
R
R
R
R
R
R
R
$000C
Data Direction Register E Read: DDRE7 (DDRE) Write: Data Direction Register F Read: (DDRF) Write: 0 R R
DDRE6 0 R = Reserved
DDRE5 0 R
DDRE4 0 R
DDRE3
DDRE2
DDRE1
DDRE0
$000D
DDRF3
DDRF2
DDRF1
DDRF0
Figure 2-2. Control, Status, and Data Register (Sheet 1 of 6)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Memory Map Advance Information 47
NON-DISCLOSURE
$0008
PTE6
PTE5
PTE4
PTE3
PTE2
PTE1
PTE0
AGREEMENT
$0003
PTD4
PTD3
PTD2
PTD1
PTD0
REQUIRED
Memory Map REQUIRED
Addr. $000E
Register Name Reserved Read: Write: Read: Write:
Bit 7 R
6 R
5 R
4 R
3 R
2 R
1 R
Bit 0 R
$000F
Reserved
R
R
R
R
R
R
R
R
$0010
SPI Control Register Read: (SPCR) Write: SPI Status and Control Register Read: (SPSCR) Write: SPI Data Register Read: (SPDR) Write:
SPRIE SPRF R R7 T7
R
SPMSTR OVRF R R5 T5 TXINV
CPOL MODF R R4 T4 M
CPHA SPTE R R3 T3 WAKE
SPWOM
SPE
SPTIE
AGREEMENT
$0011
ERRIE R6 T6 ENSCI
MODFEN R2 T2 ILTY
SPR1 R1 T1 PEN
SPR0 R0 T0 PTY
$0012
$0013
SCI Control Register 1 Read: LOOPS (SCC1) Write: SCI Control Register 2 Read: (SCC2) Write: SCI Control Register 3 Read: (SCC3) Write: SCI Status Register 1 Read: (SCS1) Write: SCI Status Register 2 Read: (SCS2) Write: SCI Data Register Read: (SCDR) Write: SCI Baud Rate Register Read: (SCBR) Write: IRQ Status and Control Read: Register (ISCR) Write: Reserved Read: Write: SCTIE R8 R SCTE R 0 R R7 T7 0 R 0 R R R
$0014
TCIE
SCRIE
ILIE
TE
RE
RWU
SBK
$0015
T8 TC R 0 R R6 T6 0 R 0 R R = Reserved
R SCRF R 0 R R5 T5 SCP1 0 R R
R IDLE R 0 R R4 T4 SCP0 0 R R
ORIE OR R 0 R R3 T3 R IRQF R R
NEIE NF R 0 R R2 T2 SCR2 0 ACK1 R
FEIE FE R BKF R R1 T1 SCR1
PEIE PE R RPF R R0 T0 SCR0
NON-DISCLOSURE
$0016
$0017
$0018
$0019
$001A
IMASK
MODE1
$001B
R
R
Figure 2-2. Control, Status, and Data Register (Sheet 2 of 6)
Advance Information 48 Memory Map MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Memory Map Input/Output (I/O) Section
Addr. $001C
Register Name PLL Control Register Read: (PCTL) Write: PLL Bandwidth Control Register Read: (PBWC) Write: PLL Programming Register Read: (PPG) Write:
Bit 7 PLLIE
6 PLLF R LOCK R MUL6
5 PLLON
4 BCS
3 1 R 0 R VRS7 SSREC R 0 R R 11 R 3 R 11
2 1 R 0 R VRS6 COPS R PS2
1 1 R 0 R VRS5 STOP R PS1
Bit 0 1 R 0 R VRS4 COPD
$001D
AUTO
ACQ
XLD
$001E
MUL7
MUL5
MUL4 LVIPWR R 0 TRST R 12 R 4 R 12
$001F
$0020
Timer Status and Control Read: Register (TSC) Write: Reserved Read: Write:
TOF 0 R Bit 15 R Bit 7 R Bit 15
TOIE
TSTOP
PS0
$0021
R 14 R 6 R 14
R 13 R 5 R 13
R 10 R 2 R 10
R 9 R 1 R 9
R Bit 8 R Bit 0 R Bit 8
$0022
Timer Counter Register High Read: (TCNTH) Write: Timer Counter Register Low Read: (TCNTL) Write: Timer Modulo Register High Read: (TMODH) Write: Timer Modulo Register Low Read: (TMODL) Write: Timer Channel 0 Status and Read: Control Register (TSC0) Write: Timer Channel 0 Register High Read: (TCH0H) Write: Timer Channel 0 Register Low Read: (TCH0L) Write: Timer Channel 1 Status and Read: Control Register (TSC1) Write:
$0023
$0024
$0025
Bit 7 CH0F 0 Bit 15
6
5
4
3
2
1
Bit 0
$0026
CH0IE
MS0B
MS0A
ELS0B
ELS0A
TOV0
CH0MAX
$0027
14
13
12
11
10
9
Bit 8
$0028
Bit 7 CH1F 0 R
6
5 0 R
4
3
2
1
Bit 0
$0029
CH1IE = Reserved
MS1A
ELS1B
ELS1A
TOV1
CH1MAX
Figure 2-2. Control, Status, and Data Register (Sheet 3 of 6)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Memory Map Advance Information 49
NON-DISCLOSURE
AGREEMENT
Mask Option Register Read: LVISTOP ROMSEC LVIRST (MOR) Write: R R R
R
REQUIRED
Memory Map REQUIRED
Addr. $002A
Register Name Timer Channel 1 Register High Read: (TCH1H) Write: Timer Channel 1 Register Low Read: (TCH1L) Write: Timer Channel 2 Status and Read: Control Register (TSC2) Write: Timer Channel 2 Register High Read: (TCH2H) Write: Timer Channel 2 Register Low Read: (TCH2L) Write: Timer Channel 3 Status and Read: Control Register (TSC3) Write: Timer Channel 3 Register High Read: (TCH3H) Write: Timer Channel 3 Register Low Read: (TCH3L) Write: Timer Channel 4 Status and Read: Control Register (TSC4) Write: Timer Channel 4 Register High Read: (TCH4H) Write: Timer Channel 4 Register Low Read: (TCH4L) Write: Timer Channel 5 Status and Read: Control Register (TSC5) Write: Timer Channel 5 Register High Read: (TCH5H) Write: Timer Channel 5 Register Low Read: (TCH5L) Write:
Bit 7 Bit 15
6 14
5 13
4 12
3 11
2 10
1 9
Bit 0 Bit 8
$002B
Bit 7 CH2F 0 Bit 15
6
5
4
3
2
1
Bit 0
$002C
CH2IE
MS2B
MS2A
ELS2B
ELS2A
TOV2
CH2MAX
AGREEMENT
$002D
14
13
12
11
10
9
Bit 8
$002E
Bit 7 CH3F 0 Bit 15
6
5 0 R 13
4
3
2
1
Bit 0
$002F
CH3IE
MS3A
ELS3B
ELS3A
TOV3
CH3MAX
$0030
14
12
11
10
9
Bit 8
$0031
Bit 7 CH4F 0 Bit 15
6
5
4
3
2
1
Bit 0
NON-DISCLOSURE
$0032
CH4IE
MS4B
MS4A
ELS4B
ELS4A
TOV4
CH4MAX
$0033
14
13
12
11
10
9
Bit 8
$0034
Bit 7 CH5F 0 Bit 15
6
5 0 R 13
4
3
2
1
Bit 0
$0035
CH5IE
MS5A
ELS5B
ELS5A
TOV5
CH5MAX
$0036
14
12
11
10
9
Bit 8
$0037
Bit 7 R
6 = Reserved
5
4
3
2
1
Bit 0
Figure 2-2. Control, Status, and Data Register (Sheet 4 of 6)
Advance Information 50 Memory Map MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Memory Map Input/Output (I/O) Section
Addr. $0038
Register Name Analog-to-Digital Status and Read: Control Register (ADSCR) Write: Analog-to-Digital Data Register Read: (ADR) Write: Analog-to-Digital Input Clock Read: Register (ADICLK) Write: BDLC Analog and Roundtrip Read: Delay Register (BARD) Write: BDLC Control Register 1 Read: (BCR1) Write: Read: Write:
Bit 7 COCO R AD7 R ADIV2
6 AIEN
5 ADCO
4 ADCH4
3 ADCH3
2 ADCH2
1 ADCH1
Bit 0 ADCH0
$0039
AD6 R ADIV1
AD5 R ADIV0 0 R R1
AD4 R ADICLK 0 R R0
AD3 R 0 R BO3 0 R TEOD I1 R BD3
AD2 R 0 R BO2 0 R TSIFR I0 R BD2
AD1 R 0 R BO1
AD0 R 0 R BO0
$003A
$003C
IMSG
CLKS
IE
WCM
$003D BDLC Control Register (BCR2)
ALOOP 0 R BD7
DLOOP 0 R BD6
RX4XE I3 R BD5
NBFS I2 R BD4
TMIFR1 0 R BD1
TMIFR0 0 R BD0
$003E
BDLC State Vector Register Read: (BSVR) Write: BDLC Data Register (BDR) Read: Write:
$003F
$FE01
SIM Reset Status Register Read: (SRSR) Write: SIM Break Flag Control Read: Register (SBFCR) Write: Reserved Read: Write:
POR R BCFE
PIN R R
COP R R
ILOP R R
ILAD R R
0 R R
LVI R R
0 R R
$FE03
$FE07
R
R
R
R
R
R
R
R
$FE0C
Break Address Register High Read: (BRKH) Write: Break Address Register Low Read: (BRKL) Write:
Bit 15
14
13
12
11
10
9
Bit 8
$FE0D
Bit 7 R
6 = Reserved
5
4
3
2
1
Bit 0
Figure 2-2. Control, Status, and Data Register (Sheet 5 of 6)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Memory Map Advance Information 51
NON-DISCLOSURE
$FE00
SIM Break Status Register Read: (SBSR) Write:
R
R
R
R
R
R
SBSW
R
AGREEMENT
$003B
ATE
RXPOL
REQUIRED
Memory Map REQUIRED
Addr. $FE0E
Register Name Break Status and Control Read: Register (BRKSCR) Write: LVI Status Register (LVISR)
Bit 7 BRKE
6 BRKA 0 R R 0 R R R R
5 0 R 0 R R
4 0 R 0 R
3 0 R 0 R
2 0 R 0 R EEBP2
1 0 R 0 R EEBP1 0 R R EEBP1 R
Bit 0 0 R 0 R EEBP0
$FE0F
Read: LVIOUT Write: R EERA
$FE1C
EEPROM Non-Volatile Register Read: (EENVR) Write:
EEPRTCT EEBP3
AGREEMENT
$FE1D
EEPROM Control Register Read: EEBCLK (EECR) Write: Reserved Read: Write: R EERA R
EEOFF
EERAS1 EERAS0
EELAT
EEPGM
$FE1E
R R R
R R R
R EEBP3 R
R EEBP2 R
R EEBP0 R
$FE1F
EEPROM Array Control Read: Register (EEACR) Write:
$FFFF
COP Control Register Read: (COPCTL) Write: R
LOW BYTE OF RESET VECTOR WRITING TO $FFFF CLEARS COP COUNTER = Reserved
NON-DISCLOSURE
Figure 2-2. Control, Status, and Data Register (Sheet 6 of 6)
Advance Information 52 Memory Map
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Memory Map Input/Output (I/O) Section
Table 2-1. Vector Addresses
Address $FFDC Low $FFDD $FFDE $FFDF $FFE0 $FFE1 $FFE2 $FFE3 $FFE4 $FFE5 $FFE6 $FFE7 $FFE8 $FFE9 $FFEA $FFEB Priority $FFEC $FFED $FFEE $FFEF $FFF0 $FFF1 $FFF2 $FFF3 $FFF4 $FFF5 $FFF6 $FFF7 $FFF8 $FFF9 $FFFA $FFFB $FFFC $FFFD High $FFFE $FFFF BDLC Vector (High) BDLC Vector (Low) ADC Vector (High) ADC Vector (Low) SCI Transmit Vector (High) SCI Transmit Vector (Low) SCI Receive Vector (High) SCI Error Vector (High) SCI Error Vector (Low) SPI Transmit Vector (High) SPI Transmit Vector (Low) SPI Receive Vector (High) SPI Receive Vector (Low) TIM Overflow Vector (High) TIM Overflow Vector (Low) TIM Channel 5 Vector (High) TIM Channel 5 Vector (Low) TIM Channel 4 Vector (High) TIM Channel 4 Vector (Low) TIM Channel 3 Vector (Low) TIM Channel 2 Vector (High) TIM Channel 2 Vector (Low) TIM Channel 1 Vector (High) TIM Channel 1 Vector (Low) TIM Channel 0 Vector (High) TIM Channel 0 Vector (Low) PLL Vector (High) PLL Vector (Low) IRQ Vector (High) IRQ Vector (Low) SWI Vector (High) SWI Vector (Low) Reset Vector (High) Reset Vector (Low) TIM Channel 3 Vector (High) SCI Receive Vector (Low) Vector
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Memory Map
Advance Information 53
NON-DISCLOSURE
AGREEMENT
REQUIRED
Memory Map REQUIRED NON-DISCLOSURE
Advance Information 54 Memory Map
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 3. Random-Access Memory (RAM)
3.1 Contents
3.2 3.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
3.2 Introduction
This section describes the 1024 bytes of random-access memory (RAM).
3.3 Functional Description
Addresses $0050-$044F are RAM locations. The location of the stack RAM is programmable. The 16-bit stack pointer allows the stack to be anywhere in the 1024-byte memory space.
NOTE:
For correct operation, the stack pointer must point only to RAM locations.
Within page zero are 176 bytes of RAM. Because the location of the stack RAM is programmable, all page zero RAM locations can be used for input/output (I/O) control and user data or code. When the stack pointer is moved from its reset location at $00FF, direct addressing mode instructions can access all page zero RAM locations efficiently. Page zero RAM, therefore, provides ideal locations for frequently accessed global variables. Before processing an interrupt, the CPU uses five bytes of the stack to save the contents of the CPU registers.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Random-Access Memory (RAM)
Advance Information 55
NON-DISCLOSURE
AGREEMENT
REQUIRED
Random-Access Memory (RAM) REQUIRED
NOTE:
For M68HC05, M6805, and M146805 compatibility, the H register is not stacked.
During a subroutine call, the CPU uses two bytes of the stack to store the return address. The stack pointer decrements during pushes and increments during pulls.
NOTE:
Be careful when using nested subroutines. The CPU could overwrite data in the RAM during a subroutine or during the interrupt stacking operation.
NON-DISCLOSURE
Advance Information 56 Random-Access Memory (RAM)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 4. Read-Only Memory (ROM)
4.1 Contents
4.2 4.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
4.2 Introduction
This section describes the 32,256 bytes of user read-only memory (ROM), 224 bytes of monitor ROM, and 36 bytes of user vectors.
4.3 Functional Description
The user ROM consists of 32,256 bytes of ROM from addresses $8000-$FDFF. The monitor ROM and vectors are located from $FE20-$FEFF. See Figure 2-1. Memory Map. Thirty-six of the user vectors, $FFDC-$FFFF, are dedicated to user-defined reset and interrupt vectors. Security has been incorporated into the MC68HC08AS32 to prevent external viewing of the ROM contents. This feature ensures that customer-developed software remains proprietary.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Read-Only Memory (ROM)
Advance Information 57
NON-DISCLOSURE
AGREEMENT
REQUIRED
Read-Only Memory (ROM) REQUIRED NON-DISCLOSURE
Advance Information 58 Read-Only Memory (ROM)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 5. Mask Options
5.1 Contents
5.2 5.3 5.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Mask Option Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
5.2 Introduction
This section describes use of mask options by custom-masked ROMs and the mask option register in the MC68HC08AS32.
5.3 Functional Description
The mask options are hard-wired connections, specified at the same time as the ROM code, which allow the user to customize the MCU. The options control the enable or disable ability of the following functions: * * * * * * * ROM security1 Resets caused by the LVI module Power to the LVI module Stop mode recovery time (32 CGMXCLK cycles or 4096 CGMXCLK cycles) COP timeout period (218-24 CGMXCLK cycles or 213-24 CGMXCLK cycles) STOP instruction Computer operating properly module (COP)
1. No security feature is absolutely secure. However, Motorola's strategy is to make reading or copying the ROM data difficult for unauthorized users.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Mask Options
Advance Information 59
NON-DISCLOSURE
AGREEMENT
REQUIRED
Mask Options REQUIRED
The mask option register ($001F) is used in the initialization of various options. For error free compatibility with the emulator OTP (M68HC908AT32CFN), a write to $001F in the MC68HC08AS32 has no effect in MCU operation.
5.4 Mask Option Register
Address: $001F Bit 7 6 5 LVIRST R 4 LVIPWR R 3 SSREC R 2 COPRS R 1 STOP R Bit 0 COPD R
AGREEMENT
Read: LVISTOP ROMSEC Write: Reset: R = Reserved R R
Unaffected by Reset
Figure 5-1. Mask Option Register (MOR) LVISTOP -- LVI Stop Mode Enable Bit LVISTOP enables the LVI module in stop mode.(See Section 10. Low-Voltage Inhibit (LVI).) 1 = LVI enabled during stop mode 0 = LVI disabled during stop mode ROMSEC -- ROM Security Bit ROMSEC enables the ROM security feature. Setting the ROMSEC bit prevents reading of the ROM contents. Access to the ROM is denied to unauthorized users of customer-specified software. 1 = ROM security enabled 0 = ROM security disabled LVIRST -- LVI Reset Enable Bit LVIRST enables the reset signal from the LVI module. (See Section 10. Low-Voltage Inhibit (LVI).) 1 = LVI module resets enabled 0 = LVI module resets disabled
NON-DISCLOSURE
Advance Information 60
MC68HC08AS32 -- Rev. 3.0 Mask Options MOTOROLA
Mask Options Mask Option Register
LVIPWR -- LVI Power Enable Bit LVIPWR enables the LVI module. (See Section 10. Low-Voltage Inhibit (LVI).) 1 = LVI module power enabled 0 = LVI module power disabled SSREC -- Short Stop Recovery Bit SSREC enables the CPU to exit stop mode with a delay of 32 CGMXCLK cycles instead of a 4096-CGMXCLK cycle delay. (See 16.6.2 Stop Mode.) 1 = Stop mode recovery after 32 CGMXCLK cycles 0 = Stop mode recovery after 4096 CGMXCLK cycles
NOTE:
If using an external crystal oscillator, do not set the SSREC bit.
COPRS -- COP Rate Select Timeout Bit COPS selects the short COP timeout period. (See Section 13. Computer Operating Properly (COP).) 1 = COP timeout period is 213-24 CGMXCLK cycles. 0 = COP timeout period is 218-24 CGMXCLK cycles. STOP -- STOP Instruction Enable Bit
COPD -- COP Disable Bit COPD disables the COP module. (See Section 13. Computer Operating Properly (COP).) 1 = COP module disabled 0 = COP module enabled
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Mask Options
Advance Information 61
NON-DISCLOSURE
STOP enables the STOP instruction. 1 = STOP instruction enabled 0 = STOP instruction treated as illegal opcode
AGREEMENT
REQUIRED
Mask Options REQUIRED NON-DISCLOSURE
Advance Information 62 Mask Options
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 6. Electrically Erasable Programmable ROM (EEPROM)
6.1 Contents
6.2 6.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
6.2 Introduction
This section describes the 512 bytes of electrically erasable programmable ROM (EEPROM).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrically Erasable Programmable ROM (EEPROM)
Advance Information 63
NON-DISCLOSURE
6.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 6.4.1 EEPROM Programming . . . . . . . . . . . . . . . . . . . . . . . . . . .64 6.4.2 EEPROM Erasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 6.4.3 EEPROM Block Protection . . . . . . . . . . . . . . . . . . . . . . . . .68 6.4.4 EEPROM Redundant Mode . . . . . . . . . . . . . . . . . . . . . . . .69 6.4.5 EEPROM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .69 6.4.6 EEPROM Control Register . . . . . . . . . . . . . . . . . . . . . . . . .70 6.4.7 EEPROM Non-volatile Register and EEPROM Array Configuration Register . . . . . . . . .72 6.4.8 Low-Power Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 6.4.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 6.4.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
AGREEMENT
REQUIRED
Electrically Erasable Programmable ROM REQUIRED 6.3 Features
EEPROM features include: * * * * * Byte, block, or bulk erasable Non-volatile redundant array option Non-volatile block protection option Non-volatile MCU configuration bits On-chip charge pump for programming/erasing
AGREEMENT
6.4 Functional Description
Addresses $0800-$09FF are EEPROM locations. The 512 bytes of EEPROM can be programmed or erased without an external voltage supply. The EEPROM has a lifetime of 10,000 write-erase cycles in the non-redundant mode. Reliability (data retention) is further extended if the redundancy option is selected. EEPROM cells are protected with a non-volatile, 128-byte, block protection option. These options are stored in the EEPROM non-volatile register (EENVR) and are loaded into the EEPROM array configuration register (EEACR) after reset or a read of EENVR. The EEPROM array also can be disabled to reduce current.
NON-DISCLOSURE
6.4.1 EEPROM Programming The unprogrammed state is a logic 1. Programming changes the state to a logic 0. Only valid EEPROM bytes in the non-protected blocks and EENVR can be programmed. When the array is configured in the redundant mode, programming the first 256 bytes ($0800-$08FF) will also program the last 256 bytes ($0900-$09FF) with the same data. Programming the EEPROM in the non-redundant mode is recommended. Program the data to both locations before entering the redundant mode.
Advance Information 64 Electrically Erasable Programmable ROM (EEPROM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrically Erasable Programmable ROM (EEPROM) Functional Description
Follow this procedure to program a byte of EEPROM. Refer to 21.5 5.0-Volt DC Electrical Characteristics Control Timing for timing values. 1. Clear EERAS1 and EERAS0 and set EELAT in the EECR ($FE1D). Set value of tEEPGM. (See Notes a and b.) 2. Write the desired data to any user EEPROM address. 3. Set the EEPGM bit. (See Note c.) 4. Wait for a time, tEEPGM, to program the byte. 6. Wait for the programming voltage time to fall, tEEFPV. 7. Clear EELAT bits. (See Note d.) 8. Repeat steps 1 through 7 for more EEPROM programming. NOTES: a. EERAS1 and EERAS0 must be cleared for programming. Otherwise, you will be in erase mode. b. Setting the EELAT bit configures the address and data buses to latch data for programming the array. Only data with a valid EEPROM address will be latched. If another consecutive valid EEPROM write occurs, this address and data will override the previous address and data. Any attempts to read other EEPROM data will read the latched data. If EELAT is set, other writes to the EECR will be allowed after a valid EEPROM write. c. The EEPGM bit cannot be set if the EELAT bit is cleared and a non-EEPROM write has occurred. This is to ensure proper programming sequence. When EEPGM is set, the on-board charge pump generates the program voltage and applies it to the user EEPROM array. When the EEPGM bit is cleared, the program voltage is removed from the array and the internal charge pump is turned off. 5. Clear the EEPGM bit.
d. Any attempt to clear both EEPGM and EELAT bits with a single instruction will clear only EEPGM to allow time for removal of high voltage from the EEPROM array.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrically Erasable Programmable ROM (EEPROM)
Advance Information 65
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrically Erasable Programmable ROM REQUIRED
6.4.2 EEPROM Erasing The unprogrammed state is a logic 1. Only the valid EEPROM bytes in the non-protected blocks and EENVR can be erased. When the array is configured in the redundant mode, erasing the first 256 bytes ($0800-$08FF) also will erase the last 256 bytes ($0900-$09FF). Follow this procedure to erase EEPROM. Refer to 21.5 5.0-Volt DC Electrical Characteristics Control Timing for timing values. 1. Clear/set EERAS1 and EERAS0 to select byte/block/bulk erase, and set EELAT in EECTL. Set value of tEEBYT/tEEBLOCK/tEEBULK. (See Note a.) 2. Write any data to the desired address for byte erase, to any address in the desired block for block erase, or to any array address for bulk erase. 3. Set the EEPGM bit. (See Note b.) 4. Wait for a time, tEEPGM, to program the byte. 5. Clear EEPGM bit. 6. Wait for the erasing voltage time to fall, tEEFPV. 7. Clear EELAT bits. (See Note c.) 8. Repeat steps 1 through 7 for more EEPROM byte/block erasing. EEBPx bit must be cleared to erase EEPROM data in the corresponding block. If any EEBPx is set, the corresponding block cannot be erased and bulk erase mode does not apply. NOTES: a. Setting the EELAT bit configures the address and data buses to latch data for erasing the array. Only valid EEPROM addresses with their data will be latched. If another consecutive valid EEPROM write occurs, this address and data will override the previous address and data. In block erase mode, any EEPROM address in the block can be used in step 2. All locations within this block will be erased. In bulk erase mode, any EEPROM address can be used to erase the whole EEPROM. EENVR is not affected with block or bulk
NON-DISCLOSURE
Advance Information 66
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Electrically Erasable Programmable ROM (EEPROM) MOTOROLA
Electrically Erasable Programmable ROM (EEPROM) Functional Description
erase. Any attempts to read other EEPROM data will read the latched data. If EELAT is set, other writes to the EECR will be allowed after a valid EEPROM write. b. To ensure the proper erasing sequence, the EEPGM bit cannot be set if the EELAT bit is cleared and a non-EEPROM write has occurred. Once EEPGM is set, the type of erase mode cannot be modified. If EEPGM is set, the on-board charge pump generates the erase voltage and applies it to the user EEPROM array. When the EEPGM bit is cleared, the erase voltage is removed from the array and the internal charge pump is turned off. c. Any attempt to clear both EEPGM and EELAT bits with a single instruction will clear only EEPGM to allow time for removal of high voltage from the EEPROM array.
In general, all bits should be erased before being programmed. However, if program/erase cycling is of concern, the following procedure can be used to minimize bit cycling in each EEPROM byte. If any bit in a byte must be changed from a 0 to a 1, the byte needs to be erased before programming. Table 6-1 summarizes the conditions for erasing before programming. Table 6-1. EEPROM Program/Erase Cycling Reduction
EEPROM Data To Be Programmed 0 0 1 1 EEPROM Data Before Programming 0 1 0 1 Erase Before Programming? No No Yes No
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrically Erasable Programmable ROM (EEPROM)
Advance Information 67
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrically Erasable Programmable ROM REQUIRED
6.4.3 EEPROM Block Protection The 512 bytes of EEPROM are divided into four 128-byte blocks. Each of these blocks can be protected separately by the EEBPx bit. Any attempt to program or erase memory locations within the protected block will not allow the program/erase voltage to be applied to the array. Table 6-2 shows the address ranges within the blocks. Table 6-2. EEPROM Array Address Blocks
AGREEMENT
Block Number (EEBPx) EEBP0 EEBP1 EEBP2 EEBP3
Address Range $0800-$087F $0880-$08FF $0900-$097F $0980-$09FF
If the EEBPx bit is set, that corresponding address block is protected. These bits are effective after a reset or a read to the EENVR register. The block protect configuration can be modified by erasing/ programming the corresponding bits in the EENVR register and then reading the EENVR register. In redundant mode, EEBP3 and EEBP2 will have no meaning.
NON-DISCLOSURE
Advance Information 68
MC68HC08AS32 -- Rev. 3.0 Electrically Erasable Programmable ROM (EEPROM) MOTOROLA
Electrically Erasable Programmable ROM (EEPROM) Functional Description
6.4.4 EEPROM Redundant Mode To extend the EEPROM data retention, the array can be placed in redundant mode. In this mode, the first 256 bytes of user EEPROM array are mapped to the last 256 bytes. Reading, programming and erasing of the first 256 EEPROM bytes ($0800-$08FF) will physically affect two bytes of EEPROM. Addressing the last 256 bytes will not be recognized. Block protection still applies but EEBP3 and EEBP2 are meaningless.
NOTE:
6.4.5 EEPROM Configuration The EEPROM non-volatile register (EENVR) contains configurations concerning block protection and redundancy. EENVR is physically located on the bottom of the EEPROM array. The contents are non-volatile and are not modified by reset. On reset, this special register loads the EEPROM configuration into a corresponding volatile EEPROM array configuration register (EEACR). Thereafter, all reads to the EENVR will reload EEACR. The EEPROM configuration can be changed by programming/erasing the EENVR like a normal EEPROM byte. The new array configuration will take effect with a system reset or a read of the EENVR.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrically Erasable Programmable ROM (EEPROM)
Advance Information 69
NON-DISCLOSURE
AGREEMENT
Before entering redundant mode, program the EEPROM in non-redundant mode.
REQUIRED
Electrically Erasable Programmable ROM REQUIRED
6.4.6 EEPROM Control Register This read/write register controls programming/erasing of the array.
Address: $FE1D Bit 7 Read: EEBCLK Write: R 0 R 0 = Reserved 0 0 0 0 Reset: 6 0 EEOFF EERAS1 EERAS0 EELAT R 0 0 5 4 3 2 1 0 EEPGM Bit 0
AGREEMENT
Figure 6-1. EEPROM Control Register (EECR) EEBCLK -- EEPROM Bus Clock Enable Bit This read/write bit determines which clock will be used to drive the internal charge pump for programming/erasing. Reset clears this bit. 1 = Bus clock drives charge pump. 0 = Internal RC oscillator drives charge pump.
NOTE:
Use the internal RC oscillator for applications in the 3- to 5-V range.
EEOFF -- EEPROM Power Down Bit This read/write bit disables the EEPROM module for lower power consumption. Any attempts to access the array will give unpredictable results. Reset clears this bit. 1 = Disable EEPROM array 0 = Enable EEPROM array
NON-DISCLOSURE
NOTE:
The EEPROM requires a recovery time, tEEOFF, to stabilize after clearing the EEOFF bit. Refer to 21.5 5.0-Volt DC Electrical Characteristics Control Timing for timing values.
Advance Information 70 Electrically Erasable Programmable ROM (EEPROM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrically Erasable Programmable ROM (EEPROM) Functional Description
EERAS1-EERAS0 -- EEPROM Erase Bits These read/write bits set the programming/erasing modes. Reset clears these bits. Table 6-3. EEPROM Program/Erase Mode Select
EEBPx 0 0 0 0 1 X = Don't Care EERAS1 0 0 1 1 X EERA0 0 1 0 1 X Mode Byte Program Byte Erase Block Erase Bulk Erase No Erase/Program
EELAT -- EEPROM Latch Control Bit This read/write bit latches the address and data buses for programming the EEPROM array. EELAT cannot be cleared if EEPGM is still set. Reset clears this bit. 1 = Buses configured for EEPROM programming 0 = Buses configured for normal read operation EEPGM -- EEPROM Program/Erase Enable Bit This read/write bit enables the internal charge pump and applies the programming/erasing voltage to the EEPROM array if the EELAT bit is set and a write to a valid EEPROM location has occurred. Reset clears the EEPGM bit. 1 = EEPROM programming/erasing power switched on 0 = EEPROM programming/erasing power switched off
NOTE:
Writing logic 0s to both the EELAT and EEPGM bits with a single instruction will clear only EEPGM. This is to allow time for the removal of high voltage.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrically Erasable Programmable ROM (EEPROM)
Advance Information 71
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrically Erasable Programmable ROM REQUIRED
6.4.7 EEPROM Non-volatile Register and EEPROM Array Configuration Register These registers configure the EEPROM array blocks for programming purposes. EEACR loads its contents from the EENVR register at reset and upon any read of the EENVR register.
Address: $FE1F Bit 7 Read: EERA R EENVR R 6 R R R = Reserved 5 R R R 4 R R R 3 EEBP3 R EENVR 2 EEBP2 R EENVR 1 EEBP1 R EENVR Bit 0 EEBP0 R EENVR
AGREEMENT
Write: Reset:
Figure 6-2. EEPROM Array Control Register (EEACR)
Address: $FE1C Bit 7 Read: Write: Reset: EERA PV R 6 R R = Reserved 5 R R 4 R R 3 EEBP3 PV 2 EEBP2 PV 1 EEBP1 PV Bit 0 EEBP0 PV
PV = Programmed Value or 1 in the Erased State
NON-DISCLOSURE
Figure 6-3. EEPROM Non-volatile Register (EENVR) EERA -- EEPROM Redundant Array Bit This programmable/erasable/readable bit in EENVR and read-only bit in EEACR configures the array in redundant mode. Reset loads EERA from EENVR to EEACR. 1 = EEPROM array in redundant mode configuration 0 = EEPROM array in normal mode configuration EEBP3-EEBP0 -- EEPROM Block Protection Bits These programmable/erasable/readable bits in EENVR and read-only bits in EEACR select blocks of EEPROM array to keep them from being programmed or erased. Reset loads EEBP[3:0] from EENVR to EEACR. See 6.4.3 EEPROM Block Protection. 1 = EEPROM array block protected 0 = EEPROM array block unprotected
Advance Information 72 Electrically Erasable Programmable ROM (EEPROM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrically Erasable Programmable ROM (EEPROM) Functional Description
6.4.8 Low-Power Modes The following subsections describe the low-power modes. 6.4.8.1 Wait Mode The WAIT instruction does not affect the EEPROM. It is possible to program the EEPROM while the MCU is in wait mode. However, if the EEPROM is inactive, power can be reduced by setting the EEOFF bit before executing the WAIT instruction. 6.4.8.2 Stop Mode The STOP instruction reduces the EEPROM power consumption to a minimum. The STOP instruction should not be executed while the high voltage is turned on (EEPGM = 1). If stop mode is entered while program/erase is in progress, high voltage will be turned off automatically. However, the EEPGM bit will remain set. When stop mode is terminated and if EEPGM is still set, the high voltage will be turned back on automatically. Program/erase time will need to be extended if program/erase is interrupted by entering stop mode. The module requires a recovery time, tEESTOP, to stabilize after leaving stop mode (see 21.5 5.0-Volt DC Electrical Characteristics Control Timing). Attempts to access the array during the recovery time will result in unpredictable behavior.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrically Erasable Programmable ROM (EEPROM)
Advance Information 73
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrically Erasable Programmable ROM REQUIRED NON-DISCLOSURE
Advance Information 74 Electrically Erasable Programmable ROM (EEPROM)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 7. Central Processor Unit (CPU)
7.1 Contents
7.2 7.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
7.4 CPU Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 7.4.1 Accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 7.4.2 Index Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 7.4.3 Stack Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 7.4.4 Program Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 7.4.5 Condition Code Register . . . . . . . . . . . . . . . . . . . . . . . . . . .81 7.5 7.6 7.7 7.8 Arithmetic/Logic Unit (ALU) . . . . . . . . . . . . . . . . . . . . . . . . . . .83 CPU During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . .83 Instruction Set Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Opcode Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
7.2 Introduction
This section describes the central processor unit (CPU). The M68HC08 CPU is an enhanced and fully object-code-compatible version of the M68HC05 CPU. The CPU08 Reference Manual (Motorola document number CPU08RM/AD) contains a description of the CPU instruction set, addressing modes, and architecture.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 75
NON-DISCLOSURE
AGREEMENT
REQUIRED
Central Processor Unit (CPU) REQUIRED 7.3 Features
Features of the CPU include: * * * * * * * * * * * Fully upward, object-code compatibility with the M68HC05 Family 16-bit stack pointer with stack manipulation instructions 16-bit index register with X-register manipulation instructions 8-MHz CPU internal bus frequency 64-Kbyte program/data memory space 16 addressing modes Memory-to-memory data moves without using accumulator Fast 8-bit by 8-bit multiply and 16-bit by 8-bit divide instructions Enhanced binary coded decimal (BCD) data handling Modular architecture with expandable internal bus definition for extension of addressing range beyond 64 Kbytes Low-power stop mode and wait mode
NON-DISCLOSURE
Advance Information 76 Central Processor Unit (CPU)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Central Processor Unit (CPU) CPU Registers
7.4 CPU Registers
Figure 7-1 shows the five CPU registers. CPU registers are not part of the memory map.
7 15 H 15 15 X
0 ACCUMULATOR (A) 0 INDEX REGISTER (H:X) 0 0 PROGRAM COUNTER (PC) STACK POINTER (SP)
7 0 V11HINZC
CONDITION CODE REGISTER (CCR)
CARRY/BORROW FLAG ZERO FLAG NEGATIVE FLAG INTERRUPT MASK HALF-CARRY FLAG TWO'S COMPLEMENT OVERFLOW FLAG
Figure 7-1. CPU Registers 7.4.1 Accumulator The accumulator is a general-purpose 8-bit register. The CPU uses the accumulator to hold operands and the results of arithmetic/logic operations.
Bit 7 Read: Write: Reset: Unaffected by Reset 6 5 4 3 2 1 Bit 0
Figure 7-2. Accumulator (A)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 77
NON-DISCLOSURE
AGREEMENT
REQUIRED
Central Processor Unit (CPU) REQUIRED
7.4.2 Index Register The 16-bit index register allows indexed addressing of a 64-Kbyte memory space. H is the upper byte of the index register, and X is the lower byte. H:X is the concatenated 16-bit index register. In the indexed addressing modes, the CPU uses the contents of the index register to determine the conditional address of the operand.
Bit 15 Read: Write: Reset: 0 0 0 0 0 0 0 0 X X X X X X X X Bit 0
AGREEMENT
14
13
12
11
10
9
8
7
6
5
4
3
2
1
X = Indeterminate
Figure 7-3. Index Register (H:X) The index register can serve also as a temporary data storage location.
NON-DISCLOSURE
Advance Information 78 Central Processor Unit (CPU)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Central Processor Unit (CPU) CPU Registers
7.4.3 Stack Pointer The stack pointer is a 16-bit register that contains the address of the next location on the stack. During a reset, the stack pointer is preset to $00FF. The reset stack pointer (RSP) instruction sets the least significant byte to $FF and does not affect the most significant byte. The stack pointer decrements as data is pushed onto the stack and increments as data is pulled from the stack. In the stack pointer 8-bit offset and 16-bit offset addressing modes, the stack pointer can function as an index register to access data on the stack. The CPU uses the contents of the stack pointer to determine the conditional address of the operand.
Bit 15 Read: Write: Reset: 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 Bit 0
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Figure 7-4. Stack Pointer (SP)
NOTE:
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 79
NON-DISCLOSURE
The location of the stack is arbitrary and may be relocated anywhere in RAM. Moving the SP out of page zero ($0000 to $00FF) frees direct address (page zero) space. For correct operation, the stack pointer must point only to RAM locations.
AGREEMENT
REQUIRED
Central Processor Unit (CPU) REQUIRED
7.4.4 Program Counter The program counter is a 16-bit register that contains the address of the next instruction or operand to be fetched. Normally, the program counter automatically increments to the next sequential memory location every time an instruction or operand is fetched. Jump, branch, and interrupt operations load the program counter with an address other than that of the next sequential location. During reset, the program counter is loaded with the reset vector address located at $FFFE and $FFFF. The vector address is the address of the first instruction to be executed after exiting the reset state.
Bit 15 Read: Write: Reset: Loaded with vector from $FFFE and $FFFF Bit 0
AGREEMENT
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Figure 7-5. Program Counter (PC)
NON-DISCLOSURE
Advance Information 80 Central Processor Unit (CPU)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Central Processor Unit (CPU) CPU Registers
7.4.5 Condition Code Register The 8-bit condition code register contains the interrupt mask and five flags that indicate the results of the instruction just executed. Bits 6 and 5 are set permanently to logic 1. The following paragraphs describe the functions of the condition code register.
Bit 7 Read: 6 5 4 3 2 1 Bit 0
V
Write: Reset: X
1
1
1
1
H
X
I
1
N
X
Z
X
C
X
X = Indeterminate
Figure 7-6. Condition Code Register (CCR) V -- Overflow Flag Bit The CPU sets the overflow flag when a two's complement overflow occurs. The signed branch instructions BGT, BGE, BLE, and BLT use the overflow flag. 1 = Overflow 0 = No overflow H -- Half-Carry Flag Bit The CPU sets the half-carry flag when a carry occurs between accumulator bits 3 and 4 during an ADD or ADC operation. The half-carry flag is required for binary coded decimal (BCD) arithmetic operations. The DAA instruction uses the states of the H and C flags to determine the appropriate correction factor. 1 = Carry between bits 3 and 4 0 = No carry between bits 3 and 4 I -- Interrupt Mask Bit When the interrupt mask is set, all maskable CPU interrupts are disabled. CPU interrupts are enabled when the interrupt mask is cleared. When a CPU interrupt occurs, the interrupt mask is set automatically after the CPU registers are saved on the stack, but before the interrupt vector is fetched. 1 = Interrupts disabled 0 = Interrupts enabled
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU) Advance Information 81
NON-DISCLOSURE
AGREEMENT
REQUIRED
Central Processor Unit (CPU) REQUIRED
NOTE:
To maintain M68HC05 compatibility, the upper byte of the index register (H) is not stacked automatically. If the interrupt service routine modifies H, then the user must stack and unstack H using the PSHH and PULH instructions.
After the I bit is cleared, the highest-priority interrupt request is serviced first. A return-from-interrupt (RTI) instruction pulls the CPU registers from the stack and restores the interrupt mask from the stack. After any reset, the interrupt mask is set and can be cleared only by the clear interrupt mask software instruction (CLI). N -- Negative Flag Bit The CPU sets the negative flag when an arithmetic operation, logic operation, or data manipulation produces a negative result, setting bit 7 of the result. 1 = Negative result 0 = Non-negative result Z -- Zero flag Bit The CPU sets the zero flag when an arithmetic operation, logic operation, or data manipulation produces a result of $00. 1 = Zero result 0 = Non-zero result C -- Carry/Borrow Flag Bit The CPU sets the carry/borrow flag when an addition operation produces a carry out of bit 7 of the accumulator or when a subtraction operation requires a borrow. Some instructions -- such as bit test and branch, shift, and rotate -- also clear or set the carry/borrow flag. 1 = Carry out of bit 7 0 = No carry out of bit 7
NON-DISCLOSURE
Advance Information 82
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Central Processor Unit (CPU) MOTOROLA
Central Processor Unit (CPU) Arithmetic/Logic Unit (ALU)
7.5 Arithmetic/Logic Unit (ALU)
The ALU performs the arithmetic and logic operations defined by the instruction set. Refer to the CPU08 Reference Manual (Motorola document number CPU08RM/AD) for a description of the instructions and addressing modes and more detail about CPU architecture.
If the break module is enabled, a break interrupt causes the CPU to execute the software interrupt instruction (SWI) at the completion of the current CPU instruction. See Section 11. Break Module (Break). The program counter vectors to $FFFC-$FFFD ($FEFC-$FEFD in monitor mode). A return-from-interrupt instruction (RTI) in the break routine ends the break interrupt and returns the MCU to normal operation if the break interrupt has been deasserted.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 83
NON-DISCLOSURE
AGREEMENT
7.6 CPU During Break Interrupts
REQUIRED
Central Processor Unit (CPU) REQUIRED 7.7 Instruction Set Summary
Table 7-1 provides a summary of the M68HC08 instruction set. Table 7-1. Instruction Set Summary (Sheet 1 of 8)
Cycles
2 3 4 4 3 2 4 5 2 3 4 4 3 2 4 5 2 2 2 3 4 4 3 2 4 5 4 1 1 4 3 5 4 1 1 4 3 5 3
Source Form
ADC #opr ADC opr ADC opr ADC opr,X ADC opr,X ADC ,X ADC opr,SP ADC opr,SP ADD #opr ADD opr ADD opr ADD opr,X ADD opr,X ADD ,X ADD opr,SP ADD opr,SP AIS #opr AIX #opr AND #opr AND opr AND opr AND opr,X AND opr,X AND ,X AND opr,SP AND opr,SP ASL opr ASLA ASLX ASL opr,X ASL ,X ASL opr,SP ASR opr ASRA ASRX ASR opr,X ASR opr,X ASR opr,SP BCC rel
Operation
Description
VH I NZC
AGREEMENT
Add with Carry
A (A) + (M) + (C)
IMM DIR EXT - IX2 IX1 IX SP1 SP2 IMM DIR EXT - IX2 IX1 IX SP1 SP2 - - - - - - IMM - - - - - - IMM IMM DIR EXT 0 - - - IX2 IX1 IX SP1 SP2 DIR INH - - INH IX1 IX SP1 DIR INH - - INH IX1 IX SP1 - - - - - - REL
A9 B9 C9 D9 E9 F9 9EE9 9ED9 AB BB CB DB EB FB 9EEB 9EDB A7 AF A4 B4 C4 D4 E4 F4 9EE4 9ED4
ii dd hh ll ee ff ff ff ee ff ii dd hh ll ee ff ff ff ee ff ii ii ii dd hh ll ee ff ff ff ee ff
Add without Carry
A (A) + (M)
Add Immediate Value (Signed) to SP Add Immediate Value (Signed) to H:X
SP (SP) + (16 M) H:X (H:X) + (16 M)
NON-DISCLOSURE
Logical AND
A (A) & (M)
Arithmetic Shift Left (Same as LSL)
C b7 b0
0
38 dd 48 58 68 ff 78 9E68 ff 37 dd 47 57 67 ff 77 9E67 ff 24 rr
Arithmetic Shift Right
b7 b0
C
Branch if Carry Bit Clear
PC (PC) + 2 + rel ? (C) = 0
Advance Information 84 Central Processor Unit (CPU)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Operand
Address Mode
Opcode
Effect on CCR
Central Processor Unit (CPU) Instruction Set Summary
Table 7-1. Instruction Set Summary (Sheet 2 of 8)
Cycles
4 4 4 4 4 4 4 4 3 3 3 3 3 3 3 3 3 3 2 3 4 4 3 2 4 5 3 3 3 3 3 3 3
Source Form
Operation
Description
VH I NZC
BCLR n, opr
Clear Bit n in M
Mn 0
DIR (b0) DIR (b1) DIR (b2) - - - - - - DIR (b3) DIR (b4) DIR (b5) DIR (b6) DIR (b7) - - - - - - REL - - - - - - REL - - - - - - REL
11 13 15 17 19 1B 1D 1F 25 27 90 92 28 29 22 24 2F 2E A5 B5 C5 D5 E5 F5 9EE5 9ED5 93 25 23 91 2C 2B 2D
dd dd dd dd dd dd dd dd rr rr rr rr rr rr rr rr rr rr ii dd hh ll ee ff ff ff ee ff rr rr rr rr rr rr rr
BEQ rel BGE opr BGT opr BHCC rel BHCS rel BHI rel BHS rel BIH rel BIL rel BIT #opr BIT opr BIT opr BIT opr,X BIT opr,X BIT ,X BIT opr,SP BIT opr,SP BLE opr BLO rel BLS rel BLT opr BMC rel BMI rel BMS rel
Branch if Equal Branch if Greater Than or Equal To (Signed Operands) Branch if Greater Than (Signed Operands) Branch if Half Carry Bit Clear Branch if Half Carry Bit Set Branch if Higher Branch if Higher or Same (Same as BCC) Branch if IRQ Pin High Branch if IRQ Pin Low
PC (PC) + 2 + rel ? (Z) = 1 PC (PC) + 2 + rel ? (N V) = 0
PC (PC) + 2 + rel ? (Z) | (N V) = 0 - - - - - - REL PC (PC) + 2 + rel ? (H) = 0 PC (PC) + 2 + rel ? (H) = 1 PC (PC) + 2 + rel ? (C) | (Z) = 0 PC (PC) + 2 + rel ? (C) = 0 PC (PC) + 2 + rel ? IRQ = 1 PC (PC) + 2 + rel ? IRQ = 0 - - - - - - REL - - - - - - REL - - - - - - REL - - - - - - REL - - - - - - REL - - - - - - REL IMM DIR EXT 0 - - - IX2 IX1 IX SP1 SP2
Bit Test
(A) & (M)
Branch if Less Than or Equal To (Signed Operands) Branch if Lower (Same as BCS) Branch if Lower or Same Branch if Less Than (Signed Operands) Branch if Interrupt Mask Clear Branch if Minus Branch if Interrupt Mask Set
PC (PC) + 2 + rel ? (Z) | (N V) = 1 - - - - - - REL PC (PC) + 2 + rel ? (C) = 1 PC (PC) + 2 + rel ? (C) | (Z) = 1 PC (PC) + 2 + rel ? (N V) =1 PC (PC) + 2 + rel ? (I) = 0 PC (PC) + 2 + rel ? (N) = 1 PC (PC) + 2 + rel ? (I) = 1 - - - - - - REL - - - - - - REL - - - - - - REL - - - - - - REL - - - - - - REL - - - - - - REL
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 85
NON-DISCLOSURE
AGREEMENT
BCS rel
Branch if Carry Bit Set (Same as BLO)
PC (PC) + 2 + rel ? (C) = 1
Operand
Address Mode
Opcode
Effect on CCR
REQUIRED
Central Processor Unit (CPU) REQUIRED
Table 7-1. Instruction Set Summary (Sheet 3 of 8)
Cycles
3 3 3 5 5 5 5 5 5 5 5 3 5 5 5 5 5 5 5 5 4 4 4 4 4 4 4 4 4 5 4 4 5 4 6 1 2 3 1 1 1 3 2 4
Source Form
BNE rel BPL rel BRA rel
Operation
Description
PC (PC) + 2 + rel ? (Z) = 0 PC (PC) + 2 + rel ? (N) = 0 PC (PC) + 2 + rel
VH I NZC
Branch if Not Equal Branch if Plus Branch Always
- - - - - - REL - - - - - - REL - - - - - - REL DIR (b0) DIR (b1) DIR (b2) - - - - - DIR (b3) DIR (b4) DIR (b5) DIR (b6) DIR (b7) - - - - - - REL DIR (b0) DIR (b1) DIR (b2) - - - - - DIR (b3) DIR (b4) DIR (b5) DIR (b6) DIR (b7) DIR (b0) DIR (b1) DIR (b2) - - - - - - DIR (b3) DIR (b4) DIR (b5) DIR (b6) DIR (b7)
26 2A 20 01 03 05 07 09 0B 0D 0F 21 00 02 04 06 08 0A 0C 0E 10 12 14 16 18 1A 1C 1E
rr rr rr dd rr dd rr dd rr dd rr dd rr dd rr dd rr dd rr rr dd rr dd rr dd rr dd rr dd rr dd rr dd rr dd rr dd dd dd dd dd dd dd dd
AGREEMENT
BRCLR n,opr,rel Branch if Bit n in M Clear
PC (PC) + 3 + rel ? (Mn) = 0
BRN rel
Branch Never
PC (PC) + 2
BRSET n,opr,rel Branch if Bit n in M Set
PC (PC) + 3 + rel ? (Mn) = 1
BSET n,opr
Set Bit n in M
Mn 1
NON-DISCLOSURE
BSR rel
Branch to Subroutine
PC (PC) + 2; push (PCL) SP (SP) - 1; push (PCH) SP (SP) - 1 PC (PC) + rel PC (PC) + 3 + rel ? (A) - (M) = $00 PC (PC) + 3 + rel ? (A) - (M) = $00 PC (PC) + 3 + rel ? (X) - (M) = $00 PC (PC) + 3 + rel ? (A) - (M) = $00 PC (PC) + 2 + rel ? (A) - (M) = $00 PC (PC) + 4 + rel ? (A) - (M) = $00 C0 I0 M $00 A $00 X $00 H $00 M $00 M $00 M $00
- - - - - - REL
AD
rr
CBEQ opr,rel CBEQA #opr,rel CBEQX #opr,rel Compare and Branch if Equal CBEQ opr,X+,rel CBEQ X+,rel CBEQ opr,SP,rel CLC CLI CLR opr CLRA CLRX CLRH CLR opr,X CLR ,X CLR opr,SP Clear Carry Bit Clear Interrupt Mask
DIR IMM - - - - - - IMM IX1+ IX+ SP1 - - - - - 0 INH - - 0 - - - INH DIR INH INH 0 - - 0 1 - INH IX1 IX SP1
31 41 51 61 71 9E61 98 9A
dd rr ii rr ii rr ff rr rr ff rr
Clear
3F dd 4F 5F 8C 6F ff 7F 9E6F ff
Advance Information 86 Central Processor Unit (CPU)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Operand
Address Mode
Opcode
Effect on CCR
Central Processor Unit (CPU) Instruction Set Summary
Table 7-1. Instruction Set Summary (Sheet 4 of 8)
Cycles
2 3 4 4 3 2 4 5 4 1 1 4 3 5 3 4 2 3 4 4 3 2 4 5 2 dd rr rr rr ff rr rr ff rr 5 3 3 5 4 6 4 1 1 4 3 5 7 ii dd hh ll ee ff ff ff ee ff 2 3 4 4 3 2 4 5
Source Form
CMP #opr CMP opr CMP opr CMP opr,X CMP opr,X CMP ,X CMP opr,SP CMP opr,SP COM opr COMA COMX COM opr,X COM ,X COM opr,SP CPHX #opr CPHX opr CPX #opr CPX opr CPX opr CPX ,X CPX opr,X CPX opr,X CPX opr,SP CPX opr,SP DAA
Operation
Description
VH I NZC
Compare A with M
(A) - (M)
IMM DIR EXT - - IX2 IX1 IX SP1 SP2 DIR INH 0 - - 1 INH IX1 IX SP1 - - IMM DIR IMM DIR EXT - - IX2 IX1 IX SP1 SP2 U - - INH
A1 B1 C1 D1 E1 F1 9EE1 9ED1
ii dd hh ll ee ff ff ff ee ff
Complement (One's Complement)
Compare H:X with M
(H:X) - (M:M + 1)
65 75 A3 B3 C3 D3 E3 F3 9EE3 9ED3 72 3B 4B 5B 6B 7B 9E6B
ii ii+1 dd ii dd hh ll ee ff ff ff ee ff
Compare X with M
(X) - (M)
Decimal Adjust A
(A)10
DEC opr DECA DECX DEC opr,X DEC ,X DEC opr,SP DIV EOR #opr EOR opr EOR opr EOR opr,X EOR opr,X EOR ,X EOR opr,SP EOR opr,SP
Decrement
M (M) - 1 A (A) - 1 X (X) - 1 M (M) - 1 M (M) - 1 M (M) - 1 A (H:A)/(X) H Remainder
DIR INH - - - INH IX1 IX SP1 - - - - INH IMM DIR EXT 0 - - - IX2 IX1 IX SP1 SP2
3A dd 4A 5A 6A ff 7A 9E6A ff 52 A8 B8 C8 D8 E8 F8 9EE8 9ED8
Divide
Exclusive OR M with A
A (A M)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 87
NON-DISCLOSURE
DBNZ opr,rel DBNZA rel DBNZX rel Decrement and Branch if Not Zero DBNZ opr,X,rel DBNZ X,rel DBNZ opr,SP,rel
A (A) - 1 or M (M) - 1 or X (X) - 1 PC (PC) + 3 + rel ? (result) 0 DIR PC (PC) + 2 + rel ? (result) 0 INH PC (PC) + 2 + rel ? (result) 0 - - - - - - INH PC (PC) + 3 + rel ? (result) 0 IX1 PC (PC) + 2 + rel ? (result) 0 IX PC (PC) + 4 + rel ? (result) 0 SP1
AGREEMENT
M (M) = $FF - (M) A (A) = $FF - (M) X (X) = $FF - (M) M (M) = $FF - (M) M (M) = $FF - (M) M (M) = $FF - (M)
33 dd 43 53 63 ff 73 9E63 ff
Operand
Address Mode
Opcode
Effect on CCR
REQUIRED
Central Processor Unit (CPU) REQUIRED
Table 7-1. Instruction Set Summary (Sheet 5 of 8)
Cycles
4 1 1 4 3 5 2 3 4 3 2 4 5 6 5 4 2 3 4 4 3 2 4 5 3 4 2 3 4 4 3 2 4 5 4 1 1 4 3 5 4 1 1 4 3 5 5 4 4 4 5
Source Form
INC opr INCA INCX INC opr,X INC ,X INC opr,SP JMP opr JMP opr JMP opr,X JMP opr,X JMP ,X JSR opr JSR opr JSR opr,X JSR opr,X JSR ,X LDA #opr LDA opr LDA opr LDA opr,X LDA opr,X LDA ,X LDA opr,SP LDA opr,SP LDHX #opr LDHX opr LDX #opr LDX opr LDX opr LDX opr,X LDX opr,X LDX ,X LDX opr,SP LDX opr,SP LSL opr LSLA LSLX LSL opr,X LSL ,X LSL opr,SP LSR opr LSRA LSRX LSR opr,X LSR ,X LSR opr,SP MOV opr,opr MOV opr,X+ MOV #opr,opr MOV X+,opr MUL
Operation
Description
M (M) + 1 A (A) + 1 X (X) + 1 M (M) + 1 M (M) + 1 M (M) + 1
VH I NZC
Increment
DIR INH - - - INH IX1 IX SP1 DIR EXT - - - - - - IX2 IX1 IX DIR EXT - - - - - - IX2 IX1 IX IMM DIR EXT 0 - - - IX2 IX1 IX SP1 SP2 0 - - - IMM DIR IMM DIR EXT 0 - - - IX2 IX1 IX SP1 SP2 DIR INH - - INH IX1 IX SP1 DIR INH - - 0 INH IX1 IX SP1 DD 0 - - - DIX+ IMD IX+D - 0 - - - 0 INH
3C dd 4C 5C 6C ff 7C 9E6C ff BC CC DC EC FC BD CD DD ED FD A6 B6 C6 D6 E6 F6 9EE6 9ED6 45 55 AE BE CE DE EE FE 9EEE 9EDE dd hh ll ee ff ff dd hh ll ee ff ff ii dd hh ll ee ff ff ff ee ff ii jj dd ii dd hh ll ee ff ff ff ee ff
AGREEMENT
Jump
PC Jump Address
Jump to Subroutine
PC (PC) + n (n = 1, 2, or 3) Push (PCL); SP (SP) - 1 Push (PCH); SP (SP) - 1 PC Unconditional Address
Load A from M
A (M)
Load H:X from M
H:X (M:M + 1)
NON-DISCLOSURE
Load X from M
X (M)
Logical Shift Left (Same as ASL)
C b7 b0
0
38 dd 48 58 68 ff 78 9E68 ff 34 dd 44 54 64 ff 74 9E64 ff 4E 5E 6E 7E 42 dd dd dd ii dd dd
Logical Shift Right
0 b7 b0
C
Move
(M)Destination (M)Source H:X (H:X) + 1 (IX+D, DIX+) X:A (X) x (A)
Unsigned multiply
Advance Information 88 Central Processor Unit (CPU)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Operand
Address Mode
Opcode
Effect on CCR
Central Processor Unit (CPU) Instruction Set Summary
Table 7-1. Instruction Set Summary (Sheet 6 of 8)
Cycles
4 1 1 4 3 5 1 3 ii dd hh ll ee ff ff ff ee ff 2 3 4 4 3 2 4 5 2 2 2 2 2 2 4 1 1 4 3 5 4 1 1 4 3 5 1 7 4
Source Form
NEG opr NEGA NEGX NEG opr,X NEG ,X NEG opr,SP NOP NSA ORA #opr ORA opr ORA opr ORA opr,X ORA opr,X ORA ,X ORA opr,SP ORA opr,SP PSHA PSHH PSHX PULA PULH PULX ROL opr ROLA ROLX ROL opr,X ROL ,X ROL opr,SP ROR opr RORA RORX ROR opr,X ROR ,X ROR opr,SP RSP
Operation
Description
VH I NZC
M -(M) = $00 - (M) A -(A) = $00 - (A) X -(X) = $00 - (X) M -(M) = $00 - (M) M -(M) = $00 - (M) None A (A[3:0]:A[7:4])
Negate (Two's Complement)
DIR INH - - INH IX1 IX SP1 - - - - - - INH - - - - - - INH IMM DIR EXT 0 - - - IX2 IX1 IX SP1 SP2 - - - - - - INH - - - - - - INH - - - - - - INH - - - - - - INH - - - - - - INH - - - - - - INH DIR INH - - INH IX1 IX SP1 DIR INH - - INH IX1 IX SP1 - - - - - - INH
30 dd 40 50 60 ff 70 9E60 ff 9D 62 AA BA CA DA EA FA 9EEA 9EDA 87 8B 89 86 8A 88 39 dd 49 59 69 ff 79 9E69 ff 36 dd 46 56 66 ff 76 9E66 ff 9C
No Operation Nibble Swap A
Operand
Address Mode
Opcode
Effect on CCR
Inclusive OR A and M
A (A) | (M)
Push A onto Stack Push H onto Stack Push X onto Stack Pull A from Stack Pull H from Stack Pull X from Stack
Push (A); SP (SP) - 1 Push (H); SP (SP) - 1 Push (X); SP (SP) - 1 SP (SP + 1); Pull (A) SP (SP + 1); Pull (H) SP (SP + 1); Pull (X)
Rotate Left through Carry
C b7 b0
Rotate Right through Carry
b7 b0
C
Reset Stack Pointer
SP $FF SP (SP) + 1; Pull (CCR) SP (SP) + 1; Pull (A) SP (SP) + 1; Pull (X) SP (SP) + 1; Pull (PCH) SP (SP) + 1; Pull (PCL) SP SP + 1; Pull (PCH) SP SP + 1; Pull (PCL)
RTI
Return from Interrupt
INH
80
RTS
Return from Subroutine
- - - - - - INH
81
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 89
NON-DISCLOSURE
AGREEMENT
REQUIRED
Central Processor Unit (CPU) REQUIRED
Table 7-1. Instruction Set Summary (Sheet 7 of 8)
Cycles
2 3 4 4 3 2 4 5 1 2 dd hh ll ee ff ff ff ee ff dd 3 4 4 3 2 4 5 4 1 dd hh ll ee ff ff ff ee ff ii dd hh ll ee ff ff ff ee ff 3 4 4 3 2 4 5 2 3 4 4 3 2 4 5 9 2 1 1
Source Form
SBC #opr SBC opr SBC opr SBC opr,X SBC opr,X SBC ,X SBC opr,SP SBC opr,SP SEC SEI STA opr STA opr STA opr,X STA opr,X STA ,X STA opr,SP STA opr,SP STHX opr STOP STX opr STX opr STX opr,X STX opr,X STX ,X STX opr,SP STX opr,SP SUB #opr SUB opr SUB opr SUB opr,X SUB opr,X SUB ,X SUB opr,SP SUB opr,SP
Operation
Description
VH I NZC
Subtract with Carry
A (A) - (M) - (C)
IMM DIR EXT - - IX2 IX1 IX SP1 SP2 - - - - - 1 INH - - 1 - - - INH DIR EXT IX2 0 - - - IX1 IX SP1 SP2 0 - - - DIR - - 0 - - - INH DIR EXT IX2 0 - - - IX1 IX SP1 SP2 IMM DIR EXT - - IX2 IX1 IX SP1 SP2
A2 B2 C2 D2 E2 F2 9EE2 9ED2 99 9B B7 C7 D7 E7 F7 9EE7 9ED7 35 8E BF CF DF EF FF 9EEF 9EDF A0 B0 C0 D0 E0 F0 9EE0 9ED0
ii dd hh ll ee ff ff ff ee ff
AGREEMENT
Set Carry Bit Set Interrupt Mask
C1 I1
Store A in M
M (A)
Store H:X in M Enable IRQ Pin; Stop Oscillator
(M:M + 1) (H:X) I 0; Stop Oscillator
Store X in M
M (X)
NON-DISCLOSURE
Subtract
A (A) - (M)
SWI
Software Interrupt
PC (PC) + 1; Push (PCL) SP (SP) - 1; Push (PCH) SP (SP) - 1; Push (X) SP (SP) - 1; Push (A) SP (SP) - 1; Push (CCR) SP (SP) - 1; I 1 PCH Interrupt Vector High Byte PCL Interrupt Vector Low Byte CCR (A) X (A) A (CCR)
- - 1 - - - INH
83
TAP TAX TPA
Transfer A to CCR Transfer A to X Transfer CCR to A
INH - - - - - - INH - - - - - - INH
84 97 85
Advance Information 90 Central Processor Unit (CPU)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Operand
Address Mode
Opcode
Effect on CCR
Central Processor Unit (CPU) Opcode Map
Table 7-1. Instruction Set Summary (Sheet 8 of 8)
Cycles
3 1 1 3 2 4 2 1 2
Source Form
TST opr TSTA TSTX TST opr,X TST ,X TST opr,SP TSX TXA TXS A C CCR dd dd rr DD DIR DIX+ ee ff EXT ff H H hh ll I ii IMD IMM INH IX IX+ IX+D IX1 IX1+ IX2 M N
Operation
Description
VH I NZC
Test for Negative or Zero
(A) - $00 or (X) - $00 or (M) - $00
DIR INH 0 - - - INH IX1 IX SP1 - - - - - - INH - - - - - - INH - - - - - - INH
3D dd 4D 5D 6D ff 7D 9E6D ff 95 9F 94
Transfer SP to H:X Transfer X to A Transfer H:X to SP
H:X (SP) + 1 A (X) (SP) (H:X) - 1
Operand
Address Mode
Opcode
Effect on CCR
() -( ) # ? : --
7.8 Opcode Map
The opcode map is provided in Table 7-2.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Central Processor Unit (CPU)
Advance Information 91
NON-DISCLOSURE
Accumulator Carry/borrow bit Condition code register Direct address of operand Direct address of operand and relative offset of branch instruction Direct to direct addressing mode Direct addressing mode Direct to indexed with post increment addressing mode High and low bytes of offset in indexed, 16-bit offset addressing Extended addressing mode Offset byte in indexed, 8-bit offset addressing Half-carry bit Index register high byte High and low bytes of operand address in extended addressing Interrupt mask Immediate operand byte Immediate source to direct destination addressing mode Immediate addressing mode Inherent addressing mode Indexed, no offset addressing mode Indexed, no offset, post increment addressing mode Indexed with post increment to direct addressing mode Indexed, 8-bit offset addressing mode Indexed, 8-bit offset, post increment addressing mode Indexed, 16-bit offset addressing mode Memory location Negative bit
n opr PC PCH PCL REL rel rr SP1 SP2 SP U V X Z & |
Any bit Operand (one or two bytes) Program counter Program counter high byte Program counter low byte Relative addressing mode Relative program counter offset byte Relative program counter offset byte Stack pointer, 8-bit offset addressing mode Stack pointer 16-bit offset addressing mode Stack pointer Undefined Overflow bit Index register low byte Zero bit Logical AND Logical OR Logical EXCLUSIVE OR Contents of Negation (two's complement) Immediate value Sign extend Loaded with If Concatenated with Set or cleared Not affected
AGREEMENT
REQUIRED
NON-DISCLOSURE
92 Central Processor Unit (CPU) MC68HC08AS32 -- Rev. 3.0 MOTOROLA Advance Information
AGREEMENT
Table 7-2. Opcode Map
REQUIRED Central Processor Unit (CPU)
Bit Manipulation DIR DIR
MSB LSB
Branch REL 2 3 BRA 2 REL 3 BRN 2 REL 3 BHI 2 REL 3 BLS 2 REL 3 BCC 2 REL 3 BCS 2 REL 3 BNE 2 REL 3 BEQ 2 REL 3 BHCC 2 REL 3 BHCS 2 REL 3 BPL 2 REL 3 BMI 2 REL 3 BMC 2 REL 3 BMS 2 REL 3 BIL 2 REL 3 BIH 2 REL
DIR 3
INH 4
Read-Modify-Write INH IX1 5 1 NEGX 1 INH 4 CBEQX 3 IMM 7 DIV 1 INH 1 COMX 1 INH 1 LSRX 1 INH 4 LDHX 2 DIR 1 RORX 1 INH 1 ASRX 1 INH 1 LSLX 1 INH 1 ROLX 1 INH 1 DECX 1 INH 3 DBNZX 2 INH 1 INCX 1 INH 1 TSTX 1 INH 4 MOV 2 DIX+ 1 CLRX 1 INH 6 4 NEG 2 IX1 5 CBEQ 3 IX1+ 3 NSA 1 INH 4 COM 2 IX1 4 LSR 2 IX1 3 CPHX 3 IMM 4 ROR 2 IX1 4 ASR 2 IX1 4 LSL 2 IX1 4 ROL 2 IX1 4 DEC 2 IX1 5 DBNZ 3 IX1 4 INC 2 IX1 3 TST 2 IX1 4 MOV 3 IMD 3 CLR 2 IX1
SP1 9E6
IX 7
Control INH INH 8 9
IMM A 2 SUB 2 IMM 2 CMP 2 IMM 2 SBC 2 IMM 2 CPX 2 IMM 2 AND 2 IMM 2 BIT 2 IMM 2 LDA 2 IMM 2 AIS 2 IMM 2 EOR 2 IMM 2 ADC 2 IMM 2 ORA 2 IMM 2 ADD 2 IMM
DIR B
EXT C 4 SUB 3 EXT 4 CMP 3 EXT 4 SBC 3 EXT 4 CPX 3 EXT 4 AND 3 EXT 4 BIT 3 EXT 4 LDA 3 EXT 4 STA 3 EXT 4 EOR 3 EXT 4 ADC 3 EXT 4 ORA 3 EXT 4 ADD 3 EXT 3 JMP 3 EXT 5 JSR 3 EXT 4 LDX 3 EXT 4 STX 3 EXT
Register/Memory IX2 SP2 D 4 SUB 3 IX2 4 CMP 3 IX2 4 SBC 3 IX2 4 CPX 3 IX2 4 AND 3 IX2 4 BIT 3 IX2 4 LDA 3 IX2 4 STA 3 IX2 4 EOR 3 IX2 4 ADC 3 IX2 4 ORA 3 IX2 4 ADD 3 IX2 4 JMP 3 IX2 6 JSR 3 IX2 4 LDX 3 IX2 4 STX 3 IX2 9ED 5 SUB 4 SP2 5 CMP 4 SP2 5 SBC 4 SP2 5 CPX 4 SP2 5 AND 4 SP2 5 BIT 4 SP2 5 LDA 4 SP2 5 STA 4 SP2 5 EOR 4 SP2 5 ADC 4 SP2 5 ORA 4 SP2 5 ADD 4 SP2
IX1 E
SP1 9EE 4 SUB 3 SP1 4 CMP 3 SP1 4 SBC 3 SP1 4 CPX 3 SP1 4 AND 3 SP1 4 BIT 3 SP1 4 LDA 3 SP1 4 STA 3 SP1 4 EOR 3 SP1 4 ADC 3 SP1 4 ORA 3 SP1 4 ADD 3 SP1
IX F
0 5 BRSET0 3 DIR 5 BRCLR0 3 DIR 5 BRSET1 3 DIR 5 BRCLR1 3 DIR 5 BRSET2 3 DIR 5 BRCLR2 3 DIR 5 BRSET3 3 DIR 5 BRCLR3 3 DIR 5 BRSET4 3 DIR 5 BRCLR4 3 DIR 5 BRSET5 3 DIR 5 BRCLR5 3 DIR 5 BRSET6 3 DIR 5 BRCLR6 3 DIR 5 BRSET7 3 DIR 5 BRCLR7 3 DIR
1 4 BSET0 2 DIR 4 BCLR0 2 DIR 4 BSET1 2 DIR 4 BCLR1 2 DIR 4 BSET2 2 DIR 4 BCLR2 2 DIR 4 BSET3 2 DIR 4 BCLR3 2 DIR 4 BSET4 2 DIR 4 BCLR4 2 DIR 4 BSET5 2 DIR 4 BCLR5 2 DIR 4 BSET6 2 DIR 4 BCLR6 2 DIR 4 BSET7 2 DIR 4 BCLR7 2 DIR
0 1 2 3 4 5 6 7 8 9 A B C D E F
4 1 NEG NEGA 2 DIR 1 INH 5 4 CBEQ CBEQA 3 DIR 3 IMM 5 MUL 1 INH 4 1 COM COMA 2 DIR 1 INH 4 1 LSR LSRA 2 DIR 1 INH 4 3 STHX LDHX 2 DIR 3 IMM 4 1 ROR RORA 2 DIR 1 INH 4 1 ASR ASRA 2 DIR 1 INH 4 1 LSL LSLA 2 DIR 1 INH 4 1 ROL ROLA 2 DIR 1 INH 4 1 DEC DECA 2 DIR 1 INH 5 3 DBNZ DBNZA 3 DIR 2 INH 4 1 INC INCA 2 DIR 1 INH 3 1 TST TSTA 2 DIR 1 INH 5 MOV 3 DD 3 1 CLR CLRA 2 DIR 1 INH
5 3 NEG NEG 3 SP1 1 IX 6 4 CBEQ CBEQ 4 SP1 2 IX+ 2 DAA 1 INH 5 3 COM COM 3 SP1 1 IX 5 3 LSR LSR 3 SP1 1 IX 4 CPHX 2 DIR 5 3 ROR ROR 3 SP1 1 IX 5 3 ASR ASR 3 SP1 1 IX 5 3 LSL LSL 3 SP1 1 IX 5 3 ROL ROL 3 SP1 1 IX 5 3 DEC DEC 3 SP1 1 IX 6 4 DBNZ DBNZ 4 SP1 2 IX 5 3 INC INC 3 SP1 1 IX 4 2 TST TST 3 SP1 1 IX 4 MOV 2 IX+D 4 2 CLR CLR 3 SP1 1 IX
7 3 RTI BGE 1 INH 2 REL 4 3 RTS BLT 1 INH 2 REL 3 BGT 2 REL 9 3 SWI BLE 1 INH 2 REL 2 2 TAP TXS 1 INH 1 INH 1 2 TPA TSX 1 INH 1 INH 2 PULA 1 INH 2 1 PSHA TAX 1 INH 1 INH 2 1 PULX CLC 1 INH 1 INH 2 1 PSHX SEC 1 INH 1 INH 2 2 PULH CLI 1 INH 1 INH 2 2 PSHH SEI 1 INH 1 INH 1 1 CLRH RSP 1 INH 1 INH 1 NOP 1 INH 1 STOP * 1 INH 1 1 WAIT TXA 1 INH 1 INH
3 SUB 2 DIR 3 CMP 2 DIR 3 SBC 2 DIR 3 CPX 2 DIR 3 AND 2 DIR 3 BIT 2 DIR 3 LDA 2 DIR 3 STA 2 DIR 3 EOR 2 DIR 3 ADC 2 DIR 3 ORA 2 DIR 3 ADD 2 DIR 2 JMP 2 DIR 4 4 BSR JSR 2 REL 2 DIR 2 3 LDX LDX 2 IMM 2 DIR 2 3 AIX STX 2 IMM 2 DIR
MSB LSB
3 SUB 2 IX1 3 CMP 2 IX1 3 SBC 2 IX1 3 CPX 2 IX1 3 AND 2 IX1 3 BIT 2 IX1 3 LDA 2 IX1 3 STA 2 IX1 3 EOR 2 IX1 3 ADC 2 IX1 3 ORA 2 IX1 3 ADD 2 IX1 3 JMP 2 IX1 5 JSR 2 IX1 5 3 LDX LDX 4 SP2 2 IX1 5 3 STX STX 4 SP2 2 IX1
2 SUB 1 IX 2 CMP 1 IX 2 SBC 1 IX 2 CPX 1 IX 2 AND 1 IX 2 BIT 1 IX 2 LDA 1 IX 2 STA 1 IX 2 EOR 1 IX 2 ADC 1 IX 2 ORA 1 IX 2 ADD 1 IX 2 JMP 1 IX 4 JSR 1 IX 4 2 LDX LDX 3 SP1 1 IX 4 2 STX STX 3 SP1 1 IX
Inherent REL Relative Immediate IX Indexed, No Offset Direct IX1 Indexed, 8-Bit Offset Extended IX2 Indexed, 16-Bit Offset Direct-Direct IMD Immediate-Direct Indexed-Direct DIX+ Direct-Indexed *Pre-byte for stack pointer indexed instructions
INH IMM DIR EXT DD IX+D
SP1 Stack Pointer, 8-Bit Offset SP2 Stack Pointer, 16-Bit Offset IX+ Indexed, No Offset with Post Increment IX1+ Indexed, 1-Byte Offset with Post Increment
0
High Byte of Opcode in Hexadecimal
Low Byte of Opcode in Hexadecimal
0
5 Cycles BRSET0 Opcode Mnemonic 3 DIR Number of Bytes / Addressing Mode
Advance Information -- MC68HC08AS32
Section 8. Clock Generator Module (CGM)
8.1 Contents
8.2 8.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
8.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 8.4.1 Crystal Oscillator Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . .95 8.4.2 Phase-Locked Loop Circuit (PLL) . . . . . . . . . . . . . . . . . . . .97 8.4.2.1 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 8.4.2.2 Acquisition and Tracking Modes . . . . . . . . . . . . . . . . . . .99 8.4.2.3 Automatic and Manual PLL Bandwidth Modes . . . . . . . .99 8.4.2.4 Programming the PLL . . . . . . . . . . . . . . . . . . . . . . . . . .101 8.4.2.5 Special Programming Exceptions . . . . . . . . . . . . . . . . .103 8.4.3 Base Clock Selector Circuit. . . . . . . . . . . . . . . . . . . . . . . .103 8.4.4 CGM External Connections. . . . . . . . . . . . . . . . . . . . . . . .104 8.5 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 8.5.1 Crystal Amplifier Input Pin (OSC1) . . . . . . . . . . . . . . . . . .105 8.5.2 Crystal Amplifier Output Pin (OSC2) . . . . . . . . . . . . . . . . .105 8.5.3 External Filter Capacitor Pin (CGMXFC). . . . . . . . . . . . . .105 8.5.4 Analog Power Pin (VDDA/VDDAREF). . . . . . . . . . . . . . . . . .106 8.5.5 Oscillator Enable Signal (SIMOSCEN) . . . . . . . . . . . . . . .106 8.5.6 Crystal Output Frequency Signal (CGMXCLK) . . . . . . . . .106 8.5.7 CGM Base Clock Output (CGMOUT) . . . . . . . . . . . . . . . .106 8.5.8 CGM CPU Interrupt (CGMINT) . . . . . . . . . . . . . . . . . . . . .106 8.6 CGM Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 8.6.1 PLL Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 8.6.2 PLL Bandwidth Control Register . . . . . . . . . . . . . . . . . . . .110 8.6.3 PLL Programming Register . . . . . . . . . . . . . . . . . . . . . . . .112 8.7 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 93
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
8.8 Special Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 8.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 8.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 8.9 CGM During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . .115
AGREEMENT
8.10 Acquisition/Lock Time Specifications . . . . . . . . . . . . . . . . . . .115 8.10.1 Acquisition/Lock Time Definitions . . . . . . . . . . . . . . . . . . .115 8.10.2 Parametric Influences on Reaction Time . . . . . . . . . . . . .117 8.10.3 Choosing a Filter Capacitor. . . . . . . . . . . . . . . . . . . . . . . .118 8.10.4 Reaction Time Calculation . . . . . . . . . . . . . . . . . . . . . . . .119
8.2 Introduction
This section describes the clock generator module (CGM). The CGM generates the crystal clock signal, CGMXCLK, which operates at the frequency of the crystal. The CGM also generates the base clock signal, CGMOUT, from which the system integration module (SIM) derives the system clocks. CGMOUT is based on either the crystal clock divided by two or the phase-locked loop (PLL) clock, CGMVCLK, divided by two. The PLL is a frequency generator designed for use with 1-MHz to 16-MHz crystals or ceramic resonators. The PLL can generate an 8-MHz bus frequency without using a 32-MHz crystal.
NON-DISCLOSURE
8.3 Features
Features of the CGM include: * * * * * Phase-locked loop with output frequency in integer multiples of the crystal reference Programmable hardware voltage-controlled oscillator (VCO) for low-jitter operation Automatic bandwidth control mode for low-jitter operation Automatic frequency lock detector CPU interrupt on entry or exit from locked condition
Advance Information 94 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) Functional Description
8.4 Functional Description
The CGM consists of three major submodules: * * * Crystal oscillator circuit -- The crystal oscillator circuit generates the constant crystal frequency clock, CGMXCLK. Phase-locked loop (PLL) -- The PLL generates the programmable VCO frequency clock, CGMVCLK. Base clock selector circuit -- This software-controlled circuit selects either CGMXCLK divided by two or the VCO clock, CGMVCLK, divided by two as the base clock, CGMOUT. The SIM derives the system clocks from CGMOUT.
Figure 8-1 shows the structure of the CGM.
8.4.1 Crystal Oscillator Circuit The crystal oscillator circuit consists of an inverting amplifier and an external crystal. The OSC1 pin is the input and the OSC2 pin is the output to the amplifier. The SIMOSCEN signal from the system integration module (SIM) enables the crystal oscillator circuit. The CGMXCLK signal is the output of the crystal oscillator circuit and runs at a rate equal to the crystal frequency. CGMXCLK is then buffered to produce CGMRCLK, the PLL reference clock. CGMXCLK can be used by other modules which require precise timing for operation. The duty cycle of CGMXCLK is not guaranteed to be 50% and depends on external factors, including the crystal and related external components. An externally generated clock also can feed the OSC1 pin of the crystal oscillator circuit. Connect the external clock to the OSC1 pin and let the OSC2 pin float.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 95
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
CRYSTAL OSCILLATOR
OSC2
CGMXCLK TO SIM, SCI, ADC, BDLC TO SIM
OSC1
SIMOSCEN CGMRDV CGMRCLK
CLOCK SELECT CIRCUIT
/2
A B S*
CGMOUT
*When S = 1, CGMOUT = B BCS USER MODE VRS[7:4] PTC3 MONITOR MODE
VDDA
CGMXFC
VSS
AGREEMENT
PHASE DETECTOR
LOOP FILTER PLL ANALOG
VOLTAGE CONTROLLED OSCILLATOR
LOCK DETECTOR
BANDWIDTH CONTROL
INTERRUPT CONTROL
CGMINT
LOCK
AUTO
ACQ
PLLIE
PLLF
MUL[7:4]
NON-DISCLOSURE
CGMVDV
FREQUENCY DIVIDER
CGMVCLK
Figure 8-1. CGM Block Diagram
Advance Information 96 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) Functional Description
Table 8-1. CGM I/O Register Summary
Addr. $001C Register Name PLL Control Register Read: (PCTL) Write: Bit 7 PLLIE R 6 PLLF PLLON BCS R R R R 5 4 3 1 2 1 1 1 Bit 0 1
$001D
PLL Bandwidth Control Register Read: (PBWC) Write:
LOCK AUTO R ACQ XLD
0 R
0 R
0 R
0 R
$001E
PLL Programming Register Read: (PPG) Write:
MUL7
MUL6
MUL5
MUL4
VRS7
VRS6
VRS5
VRS4
R
= Reserved
8.4.2 Phase-Locked Loop Circuit (PLL) The PLL is a frequency generator that can operate in either acquisition mode or tracking mode, depending on the accuracy of the output frequency. The PLL can change between acquisition and tracking modes either automatically or manually. While reading this section, refer to 21.9 CGM Operating Conditions for operating frequencies. 8.4.2.1 Circuits The PLL consists of these circuits: * * * * * Voltage-controlled oscillator (VCO) Modulo VCO frequency divider Phase detector Loop filter Lock detector
The operating range of the VCO is programmable for a wide range of frequencies and for maximum immunity to external noise, including supply and CGMXFC noise. (For maximum immunity guidelines on
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 97
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
electromagnetic compatibility, refer to document numbers AN1050/D and AN1263/D available from your Motorola sales office.) The VCO frequency is bound to a range from roughly one-half to twice the center-of-range frequency, fVRS. Modulating the voltage on the CGMXFC pin changes the frequency within this range. By design, fVRS is equal to the nominal center-of-range frequency, fNOM, 4.9152 MHz times a linear factor (L) or fNOM. CGMRCLK is the PLL reference clock, a buffered version of CGMXCLK. CGMRCLK runs at a crystal frequency, fRCLK, and is fed to the PLL through a buffer. The buffer output is the final reference clock, CGMRDV, running at a frequency equal to fRCLK. The VCO's output clock, CGMVCLK, running at a frequency, fVCLK, is fed back through a programmable modulo divider. The modulo divider reduces the VCO clock by a factor, N (see 8.4.2.4 Programming the PLL). The divider's output is the VCO feedback clock, CGMVDV, running at a frequency equal to fVCLK/N. See 21.9 CGM Operating Conditions for more information. The phase detector then compares the VCO feedback clock (CGMVDV) with the final reference clock (CGMRDV). A correction pulse is generated based on the phase difference between the two signals. The loop filter then slightly alters the dc voltage on the external capacitor connected to CGMXFC, based on the width and direction of the correction pulse. The filter can make fast or slow corrections, depending on its mode, described in 8.4.2.2 Acquisition and Tracking Modes. The value of the external capacitor and the reference frequency determines the speed of the corrections and the stability of the PLL. The lock detector compares the frequencies of the VCO feedback clock, CGMVDV, and the final reference clock, CGMRDV. Therefore, the speed of the lock detector is directly proportional to the final reference frequency, fRD. The circuit determines the mode of the PLL and the lock condition based on this comparison.
NON-DISCLOSURE
Advance Information 98
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Clock Generator Module (CGM) MOTOROLA
Clock Generator Module (CGM) Functional Description
8.4.2.2 Acquisition and Tracking Modes The PLL filter is manually or automatically configurable into one of two operating modes: * Acquisition mode -- In acquisition mode, the filter can make large (see 21.11 CGM Acquisition/Lock Time Information) frequency corrections to the VCO. This mode is used at PLL startup or when the PLL has suffered a severe noise hit and the VCO frequency is far off the desired frequency. When in acquisition mode, the ACQ bit is clear in the PLL bandwidth control register. (See 8.6.2 PLL Bandwidth Control Register.) Tracking mode -- In tracking mode, the filter makes only small (see 21.11 CGM Acquisition/Lock Time Information) corrections to the frequency of the VCO. PLL jitter is much lower in tracking mode, but the response to noise is also slower. The PLL enters tracking mode when the VCO frequency is nearly correct, such as when the PLL is selected as the base clock source. (See 8.4.3 Base Clock Selector Circuit.) The PLL is automatically in tracking mode when not in acquisition mode or when the ACQ bit is set.
*
The PLL can change the bandwidth or operational mode of the loop filter manually or automatically. In automatic bandwidth control mode (AUTO = 1), the lock detector automatically switches between acquisition and tracking modes. Automatic bandwidth control mode also is used to determine when the VCO clock, CGMVCLK, is safe to use as the source for the base clock, CGMOUT. (See 8.6.2 PLL Bandwidth Control Register.) If PLL interrupts are enabled, the software can wait for a PLL interrupt request and then check the LOCK bit. If interrupts are disabled, software can poll the LOCK bit continuously (during PLL startup, usually) or at periodic intervals. In either case, when the LOCK bit is set, the VCO clock is safe to use as the source for the base clock. (See 8.4.3 Base Clock Selector Circuit.) If the VCO is selected as the source for the base clock and the LOCK bit is clear, the PLL has suffered a severe noise hit and the
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM) Advance Information 99
NON-DISCLOSURE
8.4.2.3 Automatic and Manual PLL Bandwidth Modes
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
software must take appropriate action, depending on the application. (See 8.7 Interrupts for information and precautions on using interrupts.) The following conditions apply when the PLL is in automatic bandwidth control mode: * The ACQ bit (see 8.6.2 PLL Bandwidth Control Register) is a read-only indicator of the mode of the filter. (See 8.4.2.2 Acquisition and Tracking Modes.) The ACQ bit is set when the VCO frequency is within a certain tolerance, TRK, and is cleared when the VCO frequency is out of a certain tolerance, UNT. (See 8.10 Acquisition/Lock Time Specifications for more information.) The LOCK bit is a read-only indicator of the locked state of the PLL. The LOCK bit is set when the VCO frequency is within a certain tolerance, LOCK, and is cleared when the VCO frequency is out of a certain tolerance, UNL. (See 8.10 Acquisition/Lock Time Specifications for more information.) CPU interrupts can occur if enabled (PLLIE = 1) when the PLL's lock condition changes, toggling the LOCK bit. (See 8.6.1 PLL Control Register.)
*
AGREEMENT
* *
*
NON-DISCLOSURE
The PLL also can operate in manual mode (AUTO = 0). Manual mode is used by systems that do not require an indicator of the lock condition for proper operation. Such systems typically operate well below fBUSMAX and require fast startup. The following conditions apply when in manual mode: * ACQ is a writable control bit that controls the mode of the filter. Before turning on the PLL in manual mode, the ACQ bit must be clear. Before entering tracking mode (ACQ = 1), software must wait a given time, tACQ (see 8.10 Acquisition/Lock Time Specifications), after turning on the PLL by setting PLLON in the PLL control register (PCTL).
*
Advance Information 100 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) Functional Description
*
Software must wait a given time, tAL, after entering tracking mode before selecting the PLL as the clock source to CGMOUT (BCS = 1). The LOCK bit is disabled. CPU interrupts from the CGM are disabled.
* *
8.4.2.4 Programming the PLL Use this procedure to program the PLL: 1. Choose the desired bus frequency, fBUSDES. Example: fBUSDES = 8 MHz 2. Calculate the desired VCO frequency, fVCLKDES. fVCLKDES = 4 x fBUSDES Example: fVCLKDES = 4 x 8 MHz = 32 MHz 3. Using a reference frequency, fRCLK, equal to the crystal frequency, calculate the VCO frequency multiplier, N.
NOTE:
f VCLKDES N = round --------------------- fRCLK - 32 MHz Example: N = ------------------- = 8 4 MHz 4. Calculate the VCO frequency, fVCLK. f VCLK = N x f RCLK Example: fVCLK = 8 x 4 MHz = 32 MHz
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 101
NON-DISCLOSURE
The round function means that the result is rounded to the nearest integer.
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
5. Calculate the bus frequency, fBUS, and compare fBUS with fBUSDES. If the calculated fBUS is not within the tolerance limits of your application, select another fBUSDES or another fRCLK. f VCLK f BUS = ----------4 32 MHz Example: f BUS = ------------------- = 8 MHz 4 6. Using the value 4.9152 MHz for fNOM, calculate the VCO linear range multiplier, L. The linear range multiplier controls the frequency range of the PLL. f VCLK L = round ------------ f NOM Example: L 32 MHz ------------------------------- = 7 4.9152 MHz
AGREEMENT
=
NON-DISCLOSURE
7. Calculate the VCO center-of-range frequency, fVRS. The center-of-range frequency is the midpoint between the minimum and maximum frequencies attainable by the PLL. fVRS = L x fNOM Example: fVRS = 7 x 4.9152 MHz = 34.4 MHz
NOTE:
Exceeding the recommended maximum bus frequency or VCO frequency can crash the MCU. For proper operation,
f NOM f VRS - f VCLK -------------2
Advance Information 102 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) Functional Description
8. Program the PLL registers accordingly: a. In the upper four bits of the PLL programming register (PPG), program the binary equivalent of N. b. In the lower four bits of the PLL programming register (PPG), program the binary equivalent of L. 8.4.2.5 Special Programming Exceptions The programming method described in 8.4.2.4 Programming the PLL does not account for two possible exceptions. A value of zero for N or L is meaningless when used in the equations given. To account for these exceptions: * * A zero value for N is interpreted exactly the same as a value of one. A zero value for L disables the PLL and prevents its selection as the source for the base clock. (See 8.4.3 Base Clock Selector Circuit.)
8.4.3 Base Clock Selector Circuit This circuit is used to select either the crystal clock (CGMXCLK) or the VCO clock (CGMVCLK) as the source of the base clock (CGMOUT). The two input clocks go through a transition control circuit that waits up to three CGMXCLK cycles and three CGMVCLK cycles to change from one clock source to the other. During this time, CGMOUT is held in stasis. The output of the transition control circuit is then divided by two to correct the duty cycle. Therefore, the bus clock frequency, which is one-half of the base clock frequency, is one-fourth the frequency of the selected clock (CGMXCLK or CGMVCLK). The BCS bit in the PLL control register (PCTL) selects which clock drives CGMOUT. The VCO clock cannot be selected as the base clock source if the PLL is not turned on. The PLL cannot be turned off if the VCO clock is selected. The PLL cannot be turned on or off simultaneously with the selection or deselection of the VCO clock. The VCO clock also cannot be selected as the base clock source if the factor L is programmed to a
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 103
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
zero. This value would set up a condition inconsistent with the operation of the PLL, so that the PLL would be disabled and the crystal clock would be forced as the source of the base clock.
8.4.4 CGM External Connections In its typical configuration, the CGM requires seven external components. Five of these are for the crystal oscillator and two are for the PLL. The crystal oscillator is normally connected in a Pierce oscillator configuration, as shown in Figure 8-2. Figure 8-2 shows only the logical representation of the internal components and may not represent actual circuitry. The oscillator configuration uses five components: * * * * * Crystal, X1 Fixed capacitor, C1 Tuning capacitor, C2, can also be a fixed capacitor Feedback resistor, RB Series resistor, RS, optional
NON-DISCLOSURE
AGREEMENT
The series resistor (RS) is included in the diagram to follow strict Pierce oscillator guidelines and may not be required for all ranges of operation, especially with high-frequency crystals. Refer to the crystal manufacturer's data for more information. Figure 8-2 also shows the external components for the PLL: * * Bypass capacitor, CBYP Filter capacitor, CF
Routing should be done with great care to minimize signal cross talk and noise. (See 8.10 Acquisition/Lock Time Specifications for routing information and more information on the filter capacitor's value and its effects on PLL performance.)
Advance Information 104 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) I/O Signals
SIMOSCEN
CGMXCLK
OSC1
OSC2 RS* RB
VSS
CGMXF
CF
VDDA/VDDA VDD
CBYP
X1
C1
C2
*RS can be 0 (shorted) when used with higher-frequency crystals. Refer to manufacturer's data.
Figure 8-2. CGM External Connections
8.5 I/O Signals
The following paragraphs describe the CGM input/output (I/O) signals.
The OSC1 pin is an input to the crystal oscillator amplifier.
8.5.2 Crystal Amplifier Output Pin (OSC2) The OSC2 pin is the output of the crystal oscillator inverting amplifier.
8.5.3 External Filter Capacitor Pin (CGMXFC) The CGMXFC pin is required by the loop filter to filter out phase corrections. A small external capacitor is connected to this pin.
NOTE:
To prevent noise problems, CF should be placed as close to the CGMXFC pin as possible, with minimum routing distances and no routing of other signals across the CF connection.
Advance Information Clock Generator Module (CGM) 105
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
NON-DISCLOSURE
8.5.1 Crystal Amplifier Input Pin (OSC1)
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
8.5.4 Analog Power Pin (VDDA/VDDAREF) VDDA/VDDAREF is a power pin used by the analog portions of the PLL. Connect the VDDA/VDDAREF pin to the same voltage potential as the VDD pin.
NOTE:
Route VDDA/VDDAREF carefully for maximum noise immunity and place bypass capacitors as close as possible to the package.
AGREEMENT
8.5.5 Oscillator Enable Signal (SIMOSCEN) The SIMOSCEN signal comes from the system integration module (SIM) and enables the oscillator and PLL.
8.5.6 Crystal Output Frequency Signal (CGMXCLK) CGMXCLK is the crystal oscillator output signal. It runs at the full speed of the crystal, fXCLK, and comes directly from the crystal oscillator circuit. Figure 8-2 shows only the logical relation of CGMXCLK to OSC1 and OSC2 and may not represent the actual circuitry. The duty cycle of CGMXCLK is unknown and may depend on the crystal and other external factors. Also, the frequency and amplitude of CGMXCLK can be unstable at startup.
NON-DISCLOSURE
8.5.7 CGM Base Clock Output (CGMOUT) CGMOUT is the clock output of the CGM. This signal goes to the SIM, which generates the MCU clocks. CGMOUT is a 50% duty cycle clock running at twice the bus frequency. CGMOUT is software programmable to be either the oscillator output, CGMXCLK, divided by two or the VCO clock, CGMVCLK, divided by two.
8.5.8 CGM CPU Interrupt (CGMINT) CGMINT is the interrupt signal generated by the PLL lock detector.
Advance Information 106 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) CGM Registers
8.6 CGM Registers
These registers control and monitor operation of the CGM: * * * PLL control register (PCTL) (See 8.6.1 PLL Control Register.) PLL bandwidth control register (PBWC) (See 8.6.2 PLL Bandwidth Control Register.) PLL programming register (PPG) (See 8.6.3 PLL Programming Register.)
Table 8-2 is a summary of the CGM registers.
Table 8-2. CGM I/O Register Summary
Addr. $001C Register Name PLL Control Register Read: (PCTL) Write: Bit 7 PLLIE R 6 PLLF PLLON BCS R R R R 5 4 3 1 2 1 1 1 Bit 0 1
$001D
PLL Bandwidth Control Register Read: (PBWC) Write:
LOCK AUTO R ACQ XLD
0 R
0 R
0 R
0 R
$001E
PLL Programming Register Read: (PPG) Write:
MUL7
MUL6
MUL5
MUL4
VRS7
VRS6
VRS5
VRS4
R
= Reserved
NOTES: 1. When AUTO = 0, PLLIE is forced to logic 0 and is read-only. 2. When AUTO = 0, PLLF and LOCK read as logic 0. 3. When AUTO = 1, ACQ is read-only. 4. When PLLON = 0 or VRS[7:4] = $0, BCS is forced to logic 0 and is read-only. 5. When PLLON = 1, the PLL programming register is read-only. 6. When BCS = 1, PLLON is forced set and is read-only.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 107
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
8.6.1 PLL Control Register The PLL control register contains the interrupt enable and flag bits, the on/off switch, and the base clock selector bit.
Address: $001C Bit 7 Read: PLLIE Write: Reset: 0 R 6 PLLF PLLON R 0 = Reserved 1 0 BCS R 1 R 1 R 1 R 1 5 4 3 1 2 1 1 1 Bit 0 1
AGREEMENT
Figure 8-3. PLL Control Register (PCTL) PLLIE -- PLL Interrupt Enable Bit This read/write bit enables the PLL to generate an interrupt request when the LOCK bit toggles, setting the PLL flag, PLLF. When the AUTO bit in the PLL bandwidth control register (PBWC) is clear, PLLIE cannot be written and reads as logic 0. Reset clears the PLLIE bit. 1 = PLL interrupts enabled 0 = PLL interrupts disabled PLLF -- PLL Flag Bit This read-only bit is set whenever the LOCK bit toggles. PLLF generates an interrupt request if the PLLIE bit also is set. PLLF always reads as logic 0 when the AUTO bit in the PLL bandwidth control register (PBWC) is clear. Clear the PLLF bit by reading the PLL control register. Reset clears the PLLF bit. 1 = Change in lock condition 0 = No change in lock condition
NON-DISCLOSURE
NOTE:
Do not inadvertently clear the PLLF bit. Any read or read-modify-write operation on the PLL control register clears the PLLF bit.
Advance Information 108 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) CGM Registers
PLLON -- PLL On Bit This read/write bit activates the PLL and enables the VCO clock, CGMVCLK. PLLON cannot be cleared if the VCO clock is driving the base clock, CGMOUT (BCS = 1). (See 8.4.3 Base Clock Selector Circuit.) Reset sets this bit so that the loop can stabilize as the MCU is powering up. 1 = PLL on 0 = PLL off BCS -- Base Clock Select Bit This read/write bit selects either the crystal oscillator output, CGMXCLK, or the VCO clock, CGMVCLK, as the source of the CGM output, CGMOUT. CGMOUT frequency is one-half the frequency of the selected clock. BCS cannot be set while the PLLON bit is clear. After toggling BCS, it may take up to three CGMXCLK cycles and three CGMVCLK cycles to complete the transition from one source clock to the other. During the transition, CGMOUT is held in stasis. (See 8.4.3 Base Clock Selector Circuit.) Reset and the STOP instruction clear the BCS bit. 1 = CGMVCLK divided by two drives CGMOUT 0 = CGMXCLK divided by two drives CGMOUT
PCTL[3:0] -- Unimplemented bits These bits provide no function and always read as logic 1s.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 109
NON-DISCLOSURE
NOTE:
PLLON and BCS have built-in protection that prevents the base clock selector circuit from selecting the VCO clock as the source of the base clock if the PLL is off. Therefore, PLLON cannot be cleared when BCS is set, and BCS cannot be set when PLLON is clear. If the PLL is off (PLLON = 0), selecting CGMVCLK requires two writes to the PLL control register. (See 8.4.3 Base Clock Selector Circuit.)
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
8.6.2 PLL Bandwidth Control Register The PLL bandwidth control register: * * * * Selects automatic or manual (software-controlled) bandwidth control mode Indicates when the PLL is locked In automatic bandwidth control mode, indicates when the PLL is in acquisition or tracking mode In manual operation, forces the PLL into acquisition or tracking mode
$001D Bit 7 Read: AUTO Write: Reset: 0 R R 0 = Reserved 0 0 6 LOCK ACQ XLD R 0 R 0 R 0 R 0 5 4 3 0 2 0 1 0 Bit 0 0
AGREEMENT
Address:
Figure 8-4. PLL Bandwidth Control Register (PBWC)
NON-DISCLOSURE
AUTO -- Automatic Bandwidth Control Bit This read/write bit selects automatic or manual bandwidth control. When initializing the PLL for manual operation (AUTO = 0), clear the ACQ bit before turning on the PLL. Reset clears the AUTO bit. 1 = Automatic bandwidth control 0 = Manual bandwidth control LOCK -- Lock Indicator Bit When the AUTO bit is set, LOCK is a read-only bit that becomes set when the VCO clock, CGMVCLK, is locked (running at the programmed frequency). When the AUTO bit is clear, LOCK reads as logic 0 and has no meaning. Reset clears the LOCK bit. 1 = VCO frequency correct or locked 0 = VCO frequency incorrect or unlocked
Advance Information 110 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) CGM Registers
ACQ -- Acquisition Mode Bit When the AUTO bit is set, ACQ is a read-only bit that indicates whether the PLL is in acquisition mode or tracking mode. When the AUTO bit is clear, ACQ is a read/write bit that controls whether the PLL is in acquisition mode or tracking mode. In automatic bandwidth control mode (AUTO = 1), the last-written value from manual operation is stored in a temporary location and is recovered when manual operation resumes. Reset clears this bit, enabling acquisition mode. 1 = Tracking mode 0 = Acquisition mode XLD -- Crystal Loss Detect Bit When the VCO output (CGMVCLK) is driving CGMOUT, this read/write bit can indicate whether the crystal reference frequency is active or not. To check the status of the crystal reference, follow these steps: 1. Write a logic 1 to XLD. 2. Wait N x 4 cycles. (N is the VCO frequency multiplier.) 3. Read XLD. 1 = Crystal reference not active 0 = Crystal reference active The crystal loss detect function works only when the BCS bit is set, selecting CGMVCLK to drive CGMOUT. When BCS is clear, XLD always reads as logic 0. PBWC[3:0] -- Reserved for Test These bits enable test functions not available in user mode. To ensure software portability from development systems to user applications, software should write 0s to PBWC[3:0] whenever writing to PBWC.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 111
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
8.6.3 PLL Programming Register The PLL programming register contains the programming information for the modulo feedback divider and the programming information for the hardware configuration of the VCO.
Address: $001E Bit 7 Read: MUL7 Write: Reset: 0 1 1 0 0 1 1 0 6 MUL6 5 MUL5 4 MUL4 3 VRS7 2 VRS6 1 VRS5 Bit 0 VRS4
AGREEMENT
Figure 8-5. PLL Programming Register (PPG) MUL[7:4] -- Multiplier Select Bits These read/write bits control the modulo feedback divider that selects the VCO frequency multiplier, N. (See 8.4.2 Phase-Locked Loop Circuit (PLL).) A value of $0 in the multiplier select bits configures the modulo feedback divider the same as a value of $1. Reset initializes these bits to $6 to give a default multiply value of 6. Table 8-3. VCO Frequency Multiplier (N) Selection
MUL7:MUL6:MUL5:MUL4 0000 0001 0010 0011 VCO Frequency Multiplier (N) 1 1 2 3
NON-DISCLOSURE
1101 1110 1111
13 14 15
Advance Information 112 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) Interrupts
NOTE:
The multiplier select bits have built-in protection that prevents them from being written when the PLL is on (PLLON = 1).
VRS[7:4] -- VCO Range Select Bits These read/write bits control the hardware center-of-range linear multiplier, L, which controls the hardware center-of-range frequency, fVRS, (see 8.4.2 Phase-Locked Loop Circuit (PLL)). VRS[7:4] cannot be written when the PLLON bit in the PLL control register (PCTL) is set. (See 8.4.2.5 Special Programming Exceptions.) A value of $0 in the VCO range selects bits, disables the PLL, and clears the BCS bit in the PCTL. (See 8.4.3 Base Clock Selector Circuit and 8.4.2.5 Special Programming Exceptions for more information.) Reset initializes the bits to $6 to give a default range multiply value of 6.
NOTE:
The VCO range select bits have built-in protection that prevents them from being written when the PLL is on (PLLON = 1) and prevents selection of the VCO clock as the source of the base clock (BCS = 1) if the VCO range select bits are all clear. The VCO range select bits must be programmed correctly. Incorrect programming can result in failure of the PLL to achieve lock.
8.7 Interrupts
When the AUTO bit is set in the PLL bandwidth control register (PBWC), the PLL can generate a CPU interrupt request every time the LOCK bit changes state. The PLLIE bit in the PLL control register (PCTL) enables CPU interrupts from the PLL. PLLF, the interrupt flag in the PCTL, becomes set whether interrupts are enabled or not. When the AUTO bit is clear, CPU interrupts from the PLL are disabled and PLLF reads as logic 0. Software should read the LOCK bit after a PLL interrupt request to see if the request was due to an entry into lock or an exit from lock. When the PLL enters lock, the VCO clock, CGMVCLK, divided by two can be selected as the CGMOUT source by setting BCS in the PCTL. When the PLL exits lock, the VCO clock frequency is corrupt, and appropriate precautions should be taken. If the application is not frequency sensitive,
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 113
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
interrupts should be disabled to prevent PLL interrupt service routines from impeding software performance or from exceeding stack limitations.
NOTE:
Software can select the CGMVCLK divided by two as the CGMOUT source even if the PLL is not locked (LOCK = 0). Therefore, software should make sure the PLL is locked before setting the BCS bit.
AGREEMENT
8.8 Special Modes
The WAIT and STOP instructions put the MCU in low-power standby modes.
8.8.1 Wait Mode The WAIT instruction does not affect the CGM. Before entering wait mode, software can disengage and turn off the PLL by clearing the BCS and PLLON bits in the PLL control register (PCTL). Less power-sensitive applications can disengage the PLL without turning it off. Applications that require the PLL to wake the MCU from wait mode also can deselect the PLL output without turning off the PLL.
NON-DISCLOSURE
8.8.2 Stop Mode When the STOP instruction executes, the SIM drives the SIMOSCEN signal low, disabling the CGM and holding low all CGM outputs (CGMXCLK, CGMOUT, and CGMINT). If the STOP instruction is executed with the VCO clock (CGMVCLK) divided by two driving CGMOUT, the PLL automatically clears the BCS bit in the PLL control register (PCTL), thereby selecting the crystal clock (CGMXCLK) divided by two as the source of CGMOUT. When the MCU recovers from STOP, the crystal clock divided by two drives CGMOUT and BCS remains clear.
Advance Information 114 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) CGM During Break Interrupts
8.9 CGM During Break Interrupts
The system integration module (SIM) controls whether status bits in other modules can be cleared during the break state. The BCFE bit in the SIM break flag control register (SBFCR) enables software to clear status bits during the break state. (See 9.8.3 SIM Break Flag Control Register.) To allow software to clear status bits during a break interrupt, write a logic 1 to the BCFE bit. If a status bit is cleared during the break state, it remains cleared when the MCU exits the break state. To protect the PLLF bit during the break state, write a logic 0 to the BCFE bit. With BCFE at logic 0 (its default state), software can read and write the PLL control register during the break state without affecting the PLLF bit.
8.10 Acquisition/Lock Time Specifications
The acquisition and lock times of the PLL are, in many applications, the most critical PLL design parameters. Proper design and use of the PLL ensure the highest stability and lowest acquisition/lock times.
8.10.1 Acquisition/Lock Time Definitions Typical control systems refer to the acquisition time or lock time as the reaction time, within specified tolerances, of the system to a step input. In a PLL, the step input occurs when the PLL is turned on or when it suffers a noise hit. The tolerance usually is specified as a percent of the step input or when the output settles to the desired value plus or minus a percent of the frequency change. Therefore, the reaction time is constant in this definition, regardless of the size of the step input. For example, consider a system with a 5% acquisition time tolerance. If a command instructs the system to change from 0 Hz to 1 MHz, the acquisition time is the time taken for the frequency to reach 1 MHz 50 kHz. 50 kHz = 5% of the 1-MHz step input. If the system is operating at 1 MHz and suffers a -100-kHz noise hit, the acquisition time
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 115
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
is the time taken to return from 900 kHz to 1 MHz 5 kHz. 5 kHz = 5% of the 100-kHz step input. Other systems refer to acquisition and lock times as the time the system takes to reduce the error between the actual output and the desired output to within specified tolerances. Therefore, the acquisition time or lock time vary according to the original error in the output. Minor errors may not even be registered. Typical PLL applications prefer to use this definition because the system requires the output frequency to be within a certain tolerance of the desired frequency regardless of the size of the initial error. The discrepancy in these definitions makes it difficult to specify an acquisition or lock time for a typical PLL. Therefore, the definitions for acquisition and lock times for this module are: * Acquisition time, tACQ, is the time the PLL takes to reduce the error between the actual output frequency and the desired output frequency to less than the tracking mode entry tolerance, TRK. Acquisition time is based on an initial frequency error, [(fDES - fORIG)/fDES], of not more than 100%. In automatic bandwidth control mode (see 8.4.2.3 Automatic and Manual PLL Bandwidth Modes), acquisition time expires when the ACQ bit becomes set in the PLL bandwidth control register (PBWC). Lock time, tLock, is the time the PLL takes to reduce the error between the actual output frequency and the desired output frequency to less than the lock mode entry tolerance, Lock. Lock time is based on an initial frequency error, [(fDES - fORIG)/fDES], of not more than 100%. In automatic bandwidth control mode, lock time expires when the LOCK bit becomes set in the PLL bandwidth control register (PBWC). (See 8.4.2.3 Automatic and Manual PLL Bandwidth Modes.)
NON-DISCLOSURE
AGREEMENT
*
Obviously, the acquisition and lock times can vary according to how large the frequency error is and may be shorter or longer in many cases.
Advance Information 116 Clock Generator Module (CGM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Clock Generator Module (CGM) Acquisition/Lock Time Specifications
8.10.2 Parametric Influences on Reaction Time Acquisition and lock times are designed to be as short as possible while still providing the highest possible stability. These reaction times are not constant, however. Many factors directly and indirectly affect the acquisition time. The most critical parameter which affects the PLL reaction times is the reference frequency, fRDV. This frequency is the input to the phase detector and controls how often the PLL makes corrections. For stability, the corrections must be small compared to the desired frequency, so several corrections are required to reduce the frequency error. Therefore, the slower the reference the longer it takes to make these corrections. This parameter is also under user control via the choice of an external crystal frequency, fXCLK. Another critical parameter is the external filter capacitor. The PLL modifies the voltage on the VCO by adding or subtracting charge from this capacitor. Therefore, the rate at which the voltage changes for a given frequency error (thus change in charge) is proportional to the capacitor size. The size of the capacitor also is related to the stability of the PLL. If the capacitor is too small, the PLL cannot make small enough adjustments to the voltage and the system cannot lock. If the capacitor is too large, the PLL may not be able to adjust the voltage in a reasonable time. (See 8.10.3 Choosing a Filter Capacitor.) Also important is the operating voltage potential applied to the PLL analog portion potential (VDDA/VDDAREF). Typically, VDDA/VDDAREF is at the same potential as VDD. The power supply potential alters the characteristics of the PLL. A fixed value is best. Variable supplies, such as batteries, are acceptable if they vary within a known range at very slow speeds. Noise on the power supply is not acceptable, because it causes small frequency errors which continually change the acquisition time of the PLL.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 117
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
Temperature and processing also can affect acquisition time because the electrical characteristics of the PLL change. The part operates as specified as long as these influences stay within the specified limits. External factors, however, can cause drastic changes in the operation of the PLL. These factors include noise injected into the PLL through the filter capacitor, filter capacitor leakage, stray impedances on the circuit board, and even humidity or circuit board contamination.
AGREEMENT
8.10.3 Choosing a Filter Capacitor As described in 8.10.2 Parametric Influences on Reaction Time, the external filter capacitor, CF, is critical to the stability and reaction time of the PLL. The PLL is also dependent on reference frequency, fRDV, and supply voltage, VDD. The value of the capacitor, therefore, must be chosen with supply potential and reference frequency in mind. For proper operation, the external filter capacitor must be chosen according to the following equation. Refer to 8.4.2 Phase-Locked Loop Circuit (PLL) for the value of fRDV and 21.10 CGM Component Information for the value of CFACT. V DDA C F = C FACT ------------ f RDV- For the value of VDDA, choose the voltage potential at which the MCU is operating. If the power supply is variable, choose a value near the middle of the range of possible supply values. This equation does not always yield a commonly available capacitor size, so round to the nearest available size. If the value is between two different sizes, choose the higher value for better stability. Choosing the lower size may seem attractive for acquisition time improvement, but the PLL can become unstable. Also, always choose a capacitor with a tight tolerance (20% or better) and low dissipation.
NON-DISCLOSURE
Advance Information 118
MC68HC08AS32 -- Rev. 3.0 Clock Generator Module (CGM) MOTOROLA
Clock Generator Module (CGM) Acquisition/Lock Time Specifications
8.10.4 Reaction Time Calculation The actual acquisition and lock times can be calculated using the equations in this subsection. These equations yield nominal values under the following conditions: * * * * Correct selection of filter capacitor, CF (See 8.10.3 Choosing a Filter Capacitor.) Room temperature operation Negligible external leakage on CGMXFC Negligible noise
The K factor in the equations is derived from internal PLL parameters. KACQ is the K factor when the PLL is configured in acquisition mode, and KTRK is the K factor when the PLL is configured in tracking mode. (See 8.4.2.2 Acquisition and Tracking Modes.) V DDA 8 t ACQ = ---------------- ---------------- f RDV K ACQ V DDA 4 t AL = ---------------- ---------------- f RDV K TRK t Lock = t ACQ + t AL
NOTE:
There is an inverse proportionality between the lock time and the reference frequency.
In automatic bandwidth control mode, the acquisition and lock times are quantized into units based on the reference frequency. (See 8.4.2.3 Automatic and Manual PLL Bandwidth Modes.) A certain number of clock cycles, nACQ, is required to ascertain that the PLL is within the tracking mode entry tolerance, TRK, before exiting acquisition mode. Additionally, a certain number of clock cycles, nTRK, is required to ascertain that the PLL is within the lock mode entry tolerance, Lock. Therefore, the acquisition time, tACQ, is an integer multiple of nACQ/fRDV, and the acquisition to lock time, tAL, is an integer multiple of nTRK/fRDV.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Clock Generator Module (CGM)
Advance Information 119
NON-DISCLOSURE
AGREEMENT
REQUIRED
Clock Generator Module (CGM) REQUIRED
Refer to 8.4.2 Phase-Locked Loop Circuit (PLL) for the value of fRDV. Also, since the average frequency over the entire measurement period must be within the specified tolerance, the total time usually is longer than tLock as calculated above. In manual mode, it is usually necessary to wait considerably longer than tLock before selecting the PLL clock (see 8.4.3 Base Clock Selector Circuit), because the factors described in 8.10.2 Parametric Influences on Reaction Time can slow the lock time considerably.
NON-DISCLOSURE
Advance Information 120 Clock Generator Module (CGM)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 9. System Integration Module (SIM)
9.1 Contents
9.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
9.3 SIM Bus Clock Control and Generation . . . . . . . . . . . . . . . . .125 9.3.1 Bus Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 9.3.2 Clock Startup from POR or LVI Reset. . . . . . . . . . . . . . . .125 9.3.3 Clocks in Stop Mode and Wait Mode . . . . . . . . . . . . . . . .126 9.4 Reset and System Initialization. . . . . . . . . . . . . . . . . . . . . . . .126 9.4.1 External Pin Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 9.4.2 Active Resets from Internal Sources . . . . . . . . . . . . . . . . .128 9.4.2.1 Power-On Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 9.4.2.2 Computer Operating Properly (COP) Reset. . . . . . . . . .130 9.4.2.3 Illegal Opcode Reset . . . . . . . . . . . . . . . . . . . . . . . . . . .130 9.4.2.4 Illegal Address Reset . . . . . . . . . . . . . . . . . . . . . . . . . . .130 9.4.2.5 Low-Voltage Inhibit (LVI) Reset . . . . . . . . . . . . . . . . . . .130 9.5 SIM Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 9.5.1 SIM Counter During Power-On Reset . . . . . . . . . . . . . . . .131 9.5.2 SIM Counter During Stop Mode Recovery . . . . . . . . . . . .131 9.5.3 SIM Counter and Reset States . . . . . . . . . . . . . . . . . . . . .131 9.6 Program Exception Control. . . . . . . . . . . . . . . . . . . . . . . . . . .132 9.6.1 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 9.6.1.1 Hardware Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 9.6.1.2 SWI Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 9.6.2 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 9.6.3 Break Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 9.6.4 Status Flag Protection in Break Mode. . . . . . . . . . . . . . . .136 9.7 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 9.7.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 9.7.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 121
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
9.8 SIM Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 9.8.1 SIM Break Status Register . . . . . . . . . . . . . . . . . . . . . . . .140 9.8.2 SIM Reset Status Register . . . . . . . . . . . . . . . . . . . . . . . .142 9.8.3 SIM Break Flag Control Register. . . . . . . . . . . . . . . . . . . .143
9.2 Introduction
This section describes the system integration module (SIM), which supports up to 24 external and/or internal interrupts. The SIM is a system state controller that coordinates CPU and exception timing. Together with the central processor unit (CPU), the SIM controls all MCU activities. A block diagram of the SIM is shown in Figure 9-1. Table 9-1 is a summary of the SIM input/output (I/O) registers. The SIM is responsible for: * Bus clock generation and control for CPU and peripherals: - Stop/wait/reset/break entry and recovery - Internal clock control * * Master reset control, including power-on reset (POR) and computer operating properly (COP) timeout Interrupt control - Acknowledge timing - Arbitration control timing - Vector address generation * * CPU enable/disable timing Modular architecture expandable to 128 interrupt sources
NON-DISCLOSURE
Advance Information 122
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 System Integration Module (SIM) MOTOROLA
System Integration Module (SIM) Introduction
MODULE STOP MODULE WAIT STOP/WAIT CONTROL CPU STOP FROM CPU CPU WAIT FROM CPU SIMOSCEN TO CGM SIM COUNTER COP CLOCK
CGMXCLK FROM CGM CGMOUT FROM CGM /2
CLOCK CONTROL
CLOCK GENERATORS
INTERNAL CLOCKS
RESET PIN LOGIC
POR CONTROL RESET PIN CONTROL SIM RESET STATUS REGISTER MASTER RESET CONTROL
LVI FROM LVI MODULE ILLEGAL OPCODE FROM CPU ILLEGAL ADDRESS FROM ADDRESS MAP DECODERS COP FROM COP MODULE
RESET
INTERRUPT CONTROL AND PRIORITY DECODE
INTERRUPT SOURCES CPU INTERFACE
Figure 9-1. SIM Block Diagram Table 9-1. SIM I/O Register Summary
Addr. $FE00 $FE01 Register Name SIM Break Status Register (SBSR) SIM Reset Status Register (SRSR) Bit 7 R POR BCFE 6 R PIN R 5 R COP R 4 R ILOP R 3 R ILAD R 2 R 0 R 1 SBSW LVI R Bit 0 R 0 R
$FE03 SIM Break Flag Control Register (SBFCR)
R
= Reserved
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 123
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
Table 9-2 shows the internal signal names used in this section. Table 9-2. Signal Name Conventions
Signal Name CGMXCLK CGMVCLK CGMOUT Description Buffered version of OSC1 from clock generator module (CGM) PLL output PLL-based or OSC1-based clock output from CGM module (Bus clock = CGMOUT divided by two) Internal address bus Internal data bus Signal from the power-on reset module to the SIM Internal reset signal Read/write signal
AGREEMENT
IAB IDB PORRST IRST R/W
NON-DISCLOSURE
Advance Information 124 System Integration Module (SIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) SIM Bus Clock Control and Generation
9.3 SIM Bus Clock Control and Generation
The bus clock generator provides system clock signals for the CPU and peripherals on the MCU. The system clocks are generated from an incoming clock, CGMOUT, as shown in Figure 9-2. This clock can come from either an external oscillator or from the on-chip PLL. (See Section 8. Clock Generator Module (CGM).)
9.3.1 Bus Timing In user mode, the internal bus frequency is either the crystal oscillator output (CGMXCLK) divided by four or the PLL output (CGMVCLK) divided by four. (See Section 8. Clock Generator Module (CGM).)
9.3.2 Clock Startup from POR or LVI Reset When the power-on reset (POR) module or the low-voltage inhibit (LVI) module generates a reset, the clocks to the CPU and peripherals are inactive and held in an inactive phase until after 4096 CGMXCLK cycles. The RST pin is driven low by the SIM during this entire period. The bus clocks start upon completion of the timeout.
OSC1 CLOCK SELECT CIRCUIT
CGMXCLK
SIM COUNTER
CGMVCLK
/2
A
CGMOUT
B S* *When S = 1, CGMOUT = B
/2
BUS CLOCK GENERATORS
PLL
BCS PTC3 MONITOR MODE USER MODE
SIM
CGM
Figure 9-2. CGM Clock Signals
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 125
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
9.3.3 Clocks in Stop Mode and Wait Mode Upon exit from stop mode by an interrupt, break, or reset, the SIM allows CGMXCLK to clock the SIM counter. The CPU and peripheral clocks do not become active until after the stop delay timeout. This timeout is selectable as 4096 or 32 CGMXCLK cycles. (See 9.7.2 Stop Mode.) In wait mode, the CPU clocks are inactive. However, some modules can be programmed to be active in wait mode. Refer to the wait mode subsection of each module to see if the module is active or inactive in wait mode.
AGREEMENT
9.4 Reset and System Initialization
The MCU has these reset sources: * * * * * * Power-on reset module (POR) External reset pin (RST) Computer operating properly module (COP) Low-voltage inhibit module (LVI) Illegal opcode Illegal address
NON-DISCLOSURE
Each of these resets produces the vector $FFFE-FFFF ($FEFE-FEFF in monitor mode) and asserts the internal reset signal (IRST). IRST causes all registers to be returned to their default values and all modules to be returned to their reset states. An internal reset clears the SIM counter (see 9.5 SIM Counter), but an external reset does not. Each of the resets sets a corresponding bit in the SIM reset status register (SRSR). (See 9.8 SIM Registers.)
Advance Information 126 System Integration Module (SIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) Reset and System Initialization
9.4.1 External Pin Reset Pulling the asynchronous RST pin low halts all processing. The PIN bit of the SIM reset status register (SRSR) is set as long as RST is held low for a minimum of 67 CGMXCLK cycles, assuming that neither the POR nor the LVI was the source of the reset. See Table 9-3 for details. Figure 9-3 shows the relative timing. Table 9-3. PIN Bit Set Timing
Reset Type POR/LVI All Others Number of Cycles Required to Set PIN 4163 (4096 + 64 + 3) 67 (64 + 3)
CGMOUT
RST
IAB
PC
VECT H
VECT L
Figure 9-3. External Reset Timing
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 127
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
9.4.2 Active Resets from Internal Sources All internal reset sources actively pull the RST pin low for 32 CGMXCLK cycles to allow resetting of external peripherals. The internal reset signal IRST continues to be asserted for an additional 32 cycles. See Figure 9-4. An internal reset can be caused by an illegal address, illegal opcode, COP timeout, LVI, or POR. (See Figure 9-5. Sources of Internal Reset.) Note that for LVI or POR resets, the SIM cycles through 4096 CGMXCLK cycles during which the SIM forces the RST pin low. The internal reset signal then follows the sequence from the falling edge of RST shown in Figure 9-4. The COP reset is asynchronous to the bus clock. The active reset feature allows the part to issue a reset to peripherals and other chips within a system built around the MCU.
AGREEMENT
IRST
RST
RST PULLED LOW BY MCU 32 CYCLES 32 CYCLES
NON-DISCLOSURE
CGMXCLK
IAB
VECTOR HIGH
Figure 9-4. Internal Reset Timing
ILLEGAL ADDRESS RST ILLEGAL OPCODE RST COPRST LVI POR
INTERNAL RESET
Figure 9-5. Sources of Internal Reset
Advance Information 128 System Integration Module (SIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) Reset and System Initialization
9.4.2.1 Power-On Reset When power is first applied to the MCU, the power-on reset module (POR) generates a pulse to indicate that power-on has occurred. The external reset pin (RST) is held low while the SIM counter counts out 4096 CGMXCLK cycles. Another 64 CGMXCLK cycles later, the CPU and memories are released from reset to allow the reset vector sequence to occur. At power-on, these events occur: * * * * * * A POR pulse is generated. The internal reset signal is asserted. The SIM enables CGMOUT. Internal clocks to the CPU and modules are held inactive for 4096 CGMXCLK cycles to allow stabilization of the oscillator. The RST pin is driven low during the oscillator stabilization time. The POR bit of the SIM reset status register (SRSR) is set and all other bits in the register are cleared.
OSC1
PORRST 4096 CYCLES CGMXCLK 32 CYCLES 32 CYCLES
CGMOUT
RST
IAB
$FFFE
$FFFF
Figure 9-6. POR Recovery
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 129
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
9.4.2.2 Computer Operating Properly (COP) Reset The overflow of the COP counter causes an internal reset and sets the COP bit in the SIM reset status register (SRSR) if the COPD bit in the MOR register is at logic 0. (See Section 13. Computer Operating Properly (COP).) 9.4.2.3 Illegal Opcode Reset The SIM decodes signals from the CPU to detect illegal instructions. An illegal instruction sets the ILOP bit in the SIM reset status register (SRSR) and causes a reset.
AGREEMENT
NOTE:
A $9E opcode (pre-byte for SP instructions) followed by an $8E opcode (stop instruction) generates a stop mode recovery reset.
If the stop enable bit, STOP, in the MOR register is logic 0, the SIM treats the STOP instruction as an illegal opcode and causes an illegal opcode reset.
9.4.2.4 Illegal Address Reset An opcode fetch from an unmapped address generates an illegal address reset. The SIM verifies that the CPU is fetching an opcode prior to asserting the ILAD bit in the SIM reset status register (SRSR) and resetting the MCU. A data fetch from an unmapped address does not generate a reset. 9.4.2.5 Low-Voltage Inhibit (LVI) Reset The low-voltage inhibit (LVI) module asserts its output to the SIM when the VDD voltage falls to the VLVIF voltage. The LVI bit in the SIM reset status register (SRSR) is set and a chip reset is asserted if the LVIPWR and LVIRST bits in the CONFIG register are at logic 1. The RST pin will be held low until the SIM counts 4096 CGMXCLK cycles after VDD rises above VLVIR. Another 64 CGMXCLK cycles later, the CPU is released from reset to allow the reset vector sequence to occur. (See Section 10. Low-Voltage Inhibit (LVI).)
NON-DISCLOSURE
Advance Information 130 System Integration Module (SIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) SIM Counter
9.5 SIM Counter
The SIM counter is used by the power-on reset module (POR) and in stop mode recovery to allow the oscillator time to stabilize before enabling the internal bus (IBUS) clocks. The SIM counter also serves as a prescaler for the computer operating properly (COP) module. The SIM counter overflow supplies the clock for the COP module. The SIM counter is 12 bits long and is clocked by the falling edge of CGMXCLK.
The power-on reset module (POR) detects power applied to the MCU. At power-on, the POR circuit asserts the signal PORRST. Once the SIM is initialized, it enables the clock generation module (CGM) to drive the bus clock state machine.
9.5.2 SIM Counter During Stop Mode Recovery The SIM counter also is used for stop mode recovery. The STOP instruction clears the SIM counter. After an interrupt, break, or reset, the SIM senses the state of the short stop recovery bit, SSREC, in the MOR register. If the SSREC bit is a logic 1, then the stop recovery is reduced from the normal delay of 4096 CGMXCLK cycles down to 32 CGMXCLK cycles. This is ideal for applications using canned oscillators that do not require long startup times from stop mode. External crystal applications should use the full stop recovery time with SSREC cleared.
9.5.3 SIM Counter and Reset States External reset has no effect on the SIM counter. (See 9.7.2 Stop Mode for details.) The SIM counter is free-running after all reset states. (See 9.4.2 Active Resets from Internal Sources for counter control and internal reset recovery sequences.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 131
NON-DISCLOSURE
AGREEMENT
9.5.1 SIM Counter During Power-On Reset
REQUIRED
System Integration Module (SIM) REQUIRED 9.6 Program Exception Control
Normal, sequential program execution can be changed in three different ways: * Interrupts: - Maskable hardware CPU interrupts - Non-maskable software interrupt instruction (SWI) * Reset Break interrupts
AGREEMENT
*
9.6.1 Interrupts At the beginning of an interrupt, the CPU saves the CPU register contents on the stack and sets the interrupt mask (I bit) to prevent additional interrupts. At the end of an interrupt, the RTI instruction recovers the CPU register contents from the stack so that normal processing can resume. Figure 9-7 shows interrupt entry timing. Figure 9-9 shows interrupt recovery timing. Interrupts are latched, and arbitration is performed in the SIM at the start of interrupt processing. The arbitration result is a constant that the CPU uses to determine which vector to fetch. Once an interrupt is latched by the SIM, no other interrupt can take precedence, regardless of priority, until the latched interrupt is serviced or the I bit is cleared. (See Figure 9-8.)
MODULE INTERRUPT
NON-DISCLOSURE
I BIT
IAB
DUMMY
SP
SP - 1
SP - 2
SP - 3
SP - 4
VECT H
VECT L
START ADDR
IDB
DUMMY
PC - 1[7:0]
PC-1[15:8]
X
A
CCR
V DATA H
V DATA L
OPCODE
R/W
Figure 9-7. Hardware Interrupt Entry
Advance Information 132 System Integration Module (SIM) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) Program Exception Control
FROM RESET
YES BREAK INTERRUPT? I BIT SET?
NO
YES I BIT SET?
NO YES
IRQ0 INTERRUPT? NO
IRQ1 INTERRUPT? NO AS MANY INTERRUPTS AS EXIST ON CHIP
YES
STACK CPU REGISTERS SET I BIT LOAD PC WITH INTERRUPT VECTOR
FETCH NEXT INSTRUCTION
SWI INSTRUCTION?
YES
NO YES UNSTACK CPU REGISTERS
RTI INSTRUCTION? NO
EXECUTE INSTRUCTION
Figure 9-8. Interrupt Processing
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM) Advance Information 133
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
MODULE INTERRUPT
I BIT
IAB
SP - 4
SP - 3
SP - 2
SP - 1
SP
PC
PC + 1
IDB
CCR
A
X
PC - 1 [15:8]
PC-1[7:0]
OPCODE
OPERAND
R/W
AGREEMENT
Figure 9-9. Hardware Interrupt Recovery 9.6.1.1 Hardware Interrupts A hardware interrupt does not stop the current instruction. Processing of a hardware interrupt begins after completion of the current instruction. When the current instruction is complete, the SIM checks all pending hardware interrupts. If interrupts are not masked (I bit clear in the condition code register) and if the corresponding interrupt enable bit is set, the SIM proceeds with interrupt processing; otherwise, the next instruction is fetched and executed. If more than one interrupt is pending at the end of an instruction execution, the highest priority interrupt is serviced first. Figure 9-10 demonstrates what happens when two interrupts are pending. If an interrupt is pending upon exit from the original interrupt service routine, the pending interrupt is serviced before the LDA instruction is executed. The LDA opcode is prefetched by both the INT1 and INT2 RTI instructions. However, in the case of the INT1 RTI prefetch, this is a redundant operation.
NON-DISCLOSURE
NOTE:
To maintain compatibility with the M68HC05, M6805, and M146805 Families, the H register is not pushed on the stack during interrupt entry. If the interrupt service routine modifies the H register or uses the indexed addressing mode, software should save the H register and then restore it prior to exiting the routine.
Advance Information 134 System Integration Module (SIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) Program Exception Control
CLI LDA #$FF BACKGROUND ROUTINE
INT1
PSHH INT1 INTERRUPT SERVICE ROUTINE PULH RTI
INT2
PSHH INT2 INTERRUPT SERVICE ROUTINE PULH RTI
Figure 9-10. Interrupt Recognition Example 9.6.1.2 SWI Instruction The SWI instruction is a non-maskable instruction that causes an interrupt regardless of the state of the interrupt mask (I bit) in the condition code register.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 135
NON-DISCLOSURE
NOTE:
A software interrupt pushes PC onto the stack. A software interrupt does not push PC - 1, as a hardware interrupt does.
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
9.6.2 Reset All reset sources always have higher priority than interrupts and cannot be arbitrated.
9.6.3 Break Interrupts The break module can stop normal program flow at a software-programmable break point by asserting its break interrupt output. (See Section 11. Break Module (Break).) The SIM puts the CPU into the break state by forcing it to the SWI vector location. Refer to the break interrupt subsection of each module to see how the break state affects each module.
AGREEMENT
9.6.4 Status Flag Protection in Break Mode The SIM controls whether status flags contained in other modules can be cleared during break mode. The user can select to protect flags from being cleared by properly initializing the break clear flag enable bit (BCFE) in the SIM break flag control register (SBFCR). (See 9.8.3 SIM Break Flag Control Register.) Protecting flags in break mode ensures that set flags will not be cleared while in break mode. This protection allows registers to be freely read and written during break mode without losing status flag information. Setting the BCFE bit enables the clearing mechanisms. Once cleared in break mode, a flag remains cleared even when break mode is exited. Status flags with a 2-step clearing mechanism -- for example, a read of one register followed by the read or write of another -- are protected, even when the first step is accomplished prior to entering break mode. Upon leaving break mode, execution of the second step will clear the flag as usual.
NON-DISCLOSURE
Advance Information 136
MC68HC08AS32 -- Rev. 3.0 System Integration Module (SIM) MOTOROLA
System Integration Module (SIM) Low-Power Modes
9.7 Low-Power Modes
Executing the WAIT or STOP instruction puts the MCU in a low-power mode for standby situations. The SIM holds the CPU in a non-clocked state. The operation of each of these modes is described below. Both STOP and WAIT clear the interrupt mask (I) in the condition code register, allowing interrupts to occur.
9.7.1 Wait Mode In wait mode, the CPU clocks are inactive while one set of peripheral clocks continues to run. Figure 9-11 shows the timing for wait mode entry. A module that is active during wait mode can wake up the CPU with an interrupt if the interrupt is enabled. Stacking for the interrupt begins one cycle after the WAIT instruction during which the interrupt occurred. Refer to the wait mode subsection of each module to see if the module is active or inactive in wait mode. Some modules can be programmed to be active in wait mode. Wait mode also can be exited by a reset or break. A break interrupt during wait mode sets the SIM break stop/wait bit, SBSW, in the SIM break status register (SBSR). If the COP disable bit, COPD, in the mask option register (MOR $001F) is logic 0, then the computer operating properly module (COP) is enabled and remains active in wait mode.
IAB
WAIT ADDR
WAIT ADDR + 1
SAME
SAME
IDB
PREVIOUS DATA
NEXT OPCODE
SAME
SAME
R/W NOTE: Previous data can be operand data or the WAIT opcode, depending on the last instruction.
Figure 9-11. Wait Mode Entry Timing
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 137
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
Figure 9-12 and Figure 9-13 show the timing for wait recovery.
IAB
$6E0B
$6E0C
$00FF
$00FE
$00FD
$00FC
IDB
$A6
$A6
$A6
$01
$0B
$6E
EXITSTOPWAIT NOTE: EXITSTOPWAIT = RST pin or CPU interrupt or break interrupt
AGREEMENT
Figure 9-12. Wait Recovery from Interrupt or Break
32 CYCLES IAB $6E0B
32 CYCLES RSTVCTH RSTVCTL
IDB
$A6
$A6
$A6
RST
NON-DISCLOSURE
CGMXCLK
Figure 9-13. Wait Recovery from Internal Reset 9.7.2 Stop Mode In stop mode, the SIM counter is reset and the system clocks are disabled. An interrupt request from a module can cause an exit from stop mode. Stacking for interrupts begins after the selected stop recovery time has elapsed. Reset or break also causes an exit from stop mode. The SIM disables the clock generator module outputs (CGMOUT and CGMXCLK) in stop mode, stopping the CPU and peripherals. Stop recovery time is selectable using the short stop recovery (SSREC) bit in the MOR register ($001F). If SSREC is set, stop recovery is reduced from the normal delay of 4096 CGMXCLK cycles down to 32. This is
Advance Information 138 System Integration Module (SIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
System Integration Module (SIM) Low-Power Modes
ideal for applications using canned oscillators that do not require long startup times from stop mode.
NOTE:
External crystal applications should use the full stop recovery time by clearing the SSREC bit.
A break interrupt during stop mode sets the SIM break stop/wait bit (SBSW) in the SIM break status register (SBSR). The SIM counter is held in reset from the execution of the STOP instruction until the beginning of stop recovery. It is then used to time the recovery period. Figure 9-14 shows stop mode entry timing.
CPUSTOP
IAB
STOP ADDR
STOP ADDR + 1
SAME
SAME
IDB
PREVIOUS DATA
NEXT OPCODE
SAME
SAME
R/W NOTE: Previous data can be operand data or the STOP opcode, depending on the last instruction.
Figure 9-14. Stop Mode Entry Timing
STOP RECOVERY PERIOD CGMXCLK
INT/BREAK
IAB
STOP +1
STOP + 2
STOP + 2
SP
SP - 1
SP - 2
SP - 3
Figure 9-15. Stop Mode Recovery from Interrupt or Break
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 139
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED 9.8 SIM Registers
The SIM has three memory mapped registers.
9.8.1 SIM Break Status Register The SIM break status register contains a flag to indicate that a break caused an exit from stop mode or wait mode.
Address: $FE00 Bit 7 Read: R Write: Reset: R = Reserved 0 R R R R R SBSW R 6 5 4 3 2 1 Bit 0
AGREEMENT
Figure 9-16. SIM Break Status Register (SBSR) SBSW -- SIM Break Stop/Wait Bit This status bit is useful in applications requiring a return to wait mode or stop mode after exiting from a break interrupt. Clear SBSW by writing a logic 0 to it. Reset clears SBSW. 1 = Stop mode or wait mode exited by break interrupt 0 = Stop mode or wait mode not exited by break interrupt SBSW can be read within the break state SWI routine. The user can modify the return address on the stack by subtracting one from it. The following code is an example of this. Writing 0 to the SBSW bit clears it.
NON-DISCLOSURE
Advance Information 140
MC68HC08AS32 -- Rev. 3.0 System Integration Module (SIM) MOTOROLA
System Integration Module (SIM) SIM Registers
; This code works if the H register has been pushed onto the stack in the break service routine ; software. This code should be executed at the end of the break service routine software. ; HIBYTE LOBYTE ; EQU EQU 5 6
If not SBSW, do RTI BRCLR TST BNE DEC DOLO RETURN DEC PULH RTI SBSW,SBSR, RETURN LOBYTE,SP DOLO HIBYTE,SP LOBYTE,SP ; See if wait mode or stop mode was exited by ; break. ;If RETURNLO is not zero, ;then just decrement low byte. ;Else deal with high byte, too. ;Point to WAIT/STOP opcode. ;Restore H register.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 141
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED
9.8.2 SIM Reset Status Register This register contains six flags that show the source of the last reset. The status register will clear automatically after reading it. A power-on reset sets the POR bit and clears all other bits in the register.
Address: $FE01 Bit 7 Read: POR R 1 R 6 PIN R 0 = Reserved 5 COP R 0 4 ILOP R 0 3 ILAD R 0 2 0 R 0 1 LVI R 0 Bit 0 0 R 0
AGREEMENT
Write: Reset:
Figure 9-17. SIM Reset Status Register (SRSR) POR -- Power-On Reset Bit 1 = Last reset caused by POR circuit 0 = Read of SRSR PIN -- External Reset Bit 1 = Last reset caused by external reset pin (RST) 0 = POR or read of SRSR COP -- Computer Operating Properly Reset Bit 1 = Last reset caused by COP counter 0 = POR or read of SRSR ILOP -- Illegal Opcode Reset Bit 1 = Last reset caused by an illegal opcode 0 = POR or read of SRSR ILAD -- Illegal Address Reset Bit (opcode fetches only) 1 = Last reset caused by an opcode fetch from an illegal address 0 = POR or read of SRSR LVI -- Low-Voltage Inhibit Reset Bit 1 = Last reset was caused by the LVI circuit 0 = POR or read of SRSR
NON-DISCLOSURE
Advance Information 142
MC68HC08AS32 -- Rev. 3.0 System Integration Module (SIM) MOTOROLA
System Integration Module (SIM) SIM Registers
9.8.3 SIM Break Flag Control Register The SIM break control register contains a bit that enables software to clear status bits while the MCU is in a break state.
Address: $FE03 Bit 7 Read: BCFE Write: Reset: 0 R = Reserved R R R R R R R 6 5 4 3 2 1 Bit 0
Figure 9-18. SIM Break Flag Control Register (SBFCR) BCFE -- Break Clear Flag Enable Bit In some module registers, this read/write bit will enable software to clear status bits by accessing status registers only while the MCU is in a break state. To clear status bits during the break state, the BCFE bit must be set.This operation is important for modules with status bits which can be cleared only by being read. See the register descriptions in each module for additional details. 1 = Status bits clearable during break 0 = Status bits not clearable during break
MC68HC08AS32 -- Rev. 3.0 MOTOROLA System Integration Module (SIM)
Advance Information 143
NON-DISCLOSURE
AGREEMENT
REQUIRED
System Integration Module (SIM) REQUIRED NON-DISCLOSURE
Advance Information 144 System Integration Module (SIM)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 10. Low-Voltage Inhibit (LVI)
10.1 Contents
10.2 10.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
10.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 10.4.1 Polled LVI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 10.4.2 Forced Reset Operation . . . . . . . . . . . . . . . . . . . . . . . . . .147 10.4.3 False Reset Protection . . . . . . . . . . . . . . . . . . . . . . . . . . .148 10.5 10.6 LVI Status Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 LVI Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
10.7 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 10.7.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 10.7.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
10.2 Introduction
This section describes the low-voltage inhibit module (LVI), which monitors the voltage on the VDD pin and can force a reset when the VDD voltage falls to the LVI trip voltage.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Low-Voltage Inhibit (LVI)
Advance Information 145
NON-DISCLOSURE
AGREEMENT
REQUIRED
Low-Voltage Inhibit (LVI) REQUIRED 10.3 Features
Features of the LVI module include: * * * Programmable LVI reset Programmable power consumption Digital filtering of VDD pin level
AGREEMENT
10.4 Functional Description
Figure 10-1 shows the structure of the LVI module. The LVI is enabled out of reset. The LVI module contains a bandgap reference circuit and comparator. The LVI power bit, LVIPWR, enables the LVI to monitor VDD voltage. The LVI reset bit, LVIRST, enables the LVI module to generate a reset when VDD falls below a voltage, VLVIF , and remains at or below that level for nine or more consecutive CPU cycles. LVISTOP, enables the LVI module during stop mode. This will ensure when the STOP instruction is implemented, the LVI will continue to monitor the voltage level on VDD. LVIPWR, LVISTOP, and LVIRST are in the MOR register ($001F) (see Section 5. Mask Options). Once an LVI reset occurs, the MCU remains in reset until VDD rises above a voltage, VLVIR. The output of the comparator controls the state of the LVIOUT flag in the LVI status register (LVISR). An LVI reset also drives the RST pin low to provide low-voltage protection to external peripheral devices.
NON-DISCLOSURE
Advance Information 146
MC68HC08AS32 -- Rev. 3.0 Low-Voltage Inhibit (LVI) MOTOROLA
Low-Voltage Inhibit (LVI) Functional Description
VDD
LVIPWR FROM CONFIG CPU CLOCK LOW VDD DETECTOR VDD > VLVIR = 0 VDD < VLVIF = 1 STOP MODE FILTER BYPASS ANLGTRIP LVISTOP FROM CONFIG LVIOUT VDD DIGITAL FILTER FROM CONFIG LVIRST LVI RESET
Figure 10-1. LVI Module Block Diagram Table 10-1. LVI I/O Register Summary
Addr. $FE0F Register Name Bit 7 6 R 5 R 4 R 3 R 2 R 1 R Bit 0 R
LVI Status Register (LVISR) LVIOUT
R
= Reserved
10.4.1 Polled LVI Operation In applications that can operate at VDD levels below the VLVIF level, software can monitor VDD by polling the LVIOUT bit. In the MOR register, the LVIPWR bit must be at logic1 to enable the LVI module, and the LVIRST bit must be at logic 0 to disable LVI resets.
10.4.2 Forced Reset Operation In applications that require VDD to remain above the VLVIF level, enabling LVI resets allows the LVI module to reset the MCU when VDD falls to the VLVIF level and remains at or below that level for nine or more consecutive CPU cycles. In the MOR register, the LVIPWR and LVIRST bits must be at logic 1 to enable the LVI module and to enable LVI resets.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Low-Voltage Inhibit (LVI)
Advance Information 147
NON-DISCLOSURE
AGREEMENT
REQUIRED
Low-Voltage Inhibit (LVI) REQUIRED
10.4.3 False Reset Protection The VDD pin level is digitally filtered to reduce false resets due to power supply noise. In order for the LVI module to reset the MCU,VDD must remain at or below the VLVIF level for nine or more consecutive CPU cycles. VDD must be above VLVIR for only one CPU cycle to bring the MCU out of reset.
AGREEMENT
10.5 LVI Status Register
The LVI status register flags VDD voltages below the VLVIF level.
Address: $FE0F Bit 7 Read: Write: Reset: LVIOUT R 0 R 6 0 R 0 = Reserved 5 0 R 0 4 0 R 0 3 0 R 0 2 0 R 0 1 0 R 0 Bit 0 0 R 0
Figure 10-2. LVI Status Register (LVISR) LVIOUT -- LVI Output Bit This read-only flag becomes set when the VDD voltage falls below the VLVIF voltage or 32 to 40 CGMXCLK cycles. (See Table 10-2.) Reset clears the LVIOUT bit. Table 10-2. LVIOUT Bit Indication
VDD At Level: VDD > VLVIR VDD < VLVIF VDD < VLVIF VDD < VLVIF VLVIF < VDD < VLVIR For Number of CGMXCLK Cycles: Any < 32 CGMXCLK Cycles Between 32 and 40 CGMXCLK Cycles > 40 CGMXCLK Cycles Any 0 0 0 or 1 1 Previous Value LVIOUT
NON-DISCLOSURE
Advance Information 148
MC68HC08AS32 -- Rev. 3.0 Low-Voltage Inhibit (LVI) MOTOROLA
Low-Voltage Inhibit (LVI) LVI Interrupts
10.6 LVI Interrupts
The LVI module does not generate interrupt requests.
10.7 Low-Power Modes
The STOP and WAIT instructions put the MCU in low-power standby modes.
10.7.1 Wait Mode With the LVIPWR bit in the MOR register programmed to logic 1, the LVI module is active after a WAIT instruction. With the LVIRST bit in the MOR register programmed to logic 1, the LVI module can generate a reset and bring the MCU out of wait mode.
10.7.2 Stop Mode With the LVISTOP and LVIPWR bits in the configuration register programmed to a logic 1, the LVI module will be active after a STOP instruction. Because CPU clocks are disabled during stop mode, the LVI trip must bypass the digital filter to generate a reset and bring the MCU out of stop. With the LVIPWR bit in the MOR register programmed to logic 1 and the LVISTOP bit at a logic 0, the LVI module will be inactive after a STOP instruction.
NOTE:
If the LVIPWR bit is at logic 1, the LVISTOP bit must be at logic 0 to meet the minimum stop mode IDD specification.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Low-Voltage Inhibit (LVI)
Advance Information 149
NON-DISCLOSURE
AGREEMENT
REQUIRED
Low-Voltage Inhibit (LVI) REQUIRED NON-DISCLOSURE
Advance Information 150 Low-Voltage Inhibit (LVI)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 11. Break Module (Break)
11.1 Contents
11.2 11.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
11.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 11.4.1 Flag Protection During Break Interrupts . . . . . . . . . . . . . .153 11.4.2 CPU During Break Interrupts. . . . . . . . . . . . . . . . . . . . . . .154 11.4.3 TIM During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . .154 11.4.4 COP During Break Interrupts . . . . . . . . . . . . . . . . . . . . . .154 11.5 Break Module Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 11.5.1 Break Status and Control Register . . . . . . . . . . . . . . . . . .155 11.5.2 Break Address Registers. . . . . . . . . . . . . . . . . . . . . . . . . .156 11.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 11.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 11.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
11.2 Introduction
This section describes the break module (break). The break module can generate a break interrupt that stops normal program flow at a defined address to enter a background program.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Break Module (Break)
Advance Information 151
NON-DISCLOSURE
AGREEMENT
REQUIRED
Break Module (Break) REQUIRED 11.3 Features
Features of the break module include: * * * * Accessible I/O registers during the break interrupt CPU-generated break interrupts Software-generated break interrupts COP disabling during break interrupts
AGREEMENT
11.4 Functional Description
When the internal address bus matches the value written in the break address registers, the break module issues a breakpoint signal (BKPT) to the SIM. The SIM then causes the CPU to load the instruction register with a software interrupt instruction (SWI) after completion of the current CPU instruction. The program counter vectors to $FFFC and $FFFD ($FEFC and $FEFD in monitor mode). These events can cause a break interrupt to occur: * A CPU-generated address (the address in the program counter) matches the contents of the break address registers Software writes a logic 1 to the BRKA bit in the break status and control register.
NON-DISCLOSURE
*
When a CPU-generated address matches the contents of the break address registers, the break interrupt begins after the CPU completes its current instruction. A return-from-interrupt instruction (RTI) in the break routine ends the break interrupt and returns the MCU to normal operation. Figure 11-1 shows the structure of the break module.
Advance Information 152 Break Module (Break)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Break Module (Break) Functional Description
IAB[15:8]
BREAK ADDRESS REGISTER HIGH 8-BIT COMPARATOR IAB[15:0] CONTROL 8-BIT COMPARATOR BREAK ADDRESS REGISTER LOW BKPT TO SIM
Figure 11-1. Break Module Block Diagram
Table 11-1. Break I/O Register Summary
Addr. $FE0C Register Name Bit 7 6 BIT 14 5 BIT 13 4 BIT 12 3 BIT 11 2 BIT 10 1 BIT 9 Bit 0 BIT 8
Break Address Register High (BRKH) BIT 15
$FE0D
Break Address Register Low (BRKL)
BIT 7
BIT 6
BIT 5
BIT 4
BIT 3
BIT 2
BIT 1
BIT 0
$FE0E
Break Status/Control Register (BRKSCR) BRKE
BRKA
R
R
R
R
R
R
R
= Reserved
11.4.1 Flag Protection During Break Interrupts The system integration module (SIM) controls whether module status bits can be cleared during the break state. The BCFE bit in the SIM break flag control register (SBFCR) enables software to clear status bits during the break state. (See 9.8.3 SIM Break Flag Control Register and the Break Interrupts subsection for each module.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Break Module (Break)
Advance Information 153
NON-DISCLOSURE
AGREEMENT
IAB[7:0]
REQUIRED
Break Module (Break) REQUIRED
11.4.2 CPU During Break Interrupts The CPU starts a break interrupt by: * * Loading the instruction register with the SWI instruction Loading the program counter with $FFFC-$FFFD ($FEFC-$FEFD in monitor mode)
AGREEMENT
The break interrupt begins after completion of the CPU instruction in progress. If the break address register match occurs on the last cycle of a CPU instruction, the break interrupt begins immediately.
11.4.3 TIM During Break Interrupts A break interrupt stops the timer counter.
11.4.4 COP During Break Interrupts The COP is disabled during a break interrupt when VDD + VHI is present on the RST pin. For VHI, see 21.5 5.0-Volt DC Electrical Characteristics Control Timing.
NON-DISCLOSURE
11.5 Break Module Registers
Three registers control and monitor operation of the break module: * * * Break status and control register (BRKSCR) Break address register high (BRKH) Break address register low (BRKL)
Advance Information 154 Break Module (Break)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Break Module (Break) Break Module Registers
11.5.1 Break Status and Control Register The break status and control register contains break module enable and status bits.
Address: $FE0E Bit 7 Read: BRKE Write: Reset: 0 R 0 = Reserved BRKA R 0 R 0 R 0 R 0 R 0 R 0 6 5 0 4 0 3 0 2 0 1 0 Bit 0 0
Figure 11-2. Break Status and Control Register (BRKSCR) BRKE -- Break Enable Bit This read/write bit enables breaks on break address register matches. Clear BRKE by writing a logic 0 to bit 7. Reset clears the BRKE bit. 1 = Breaks enabled on 16-bit address match 0 = Breaks disabled on 16-bit address match BRKA -- Break Active Bit
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Break Module (Break)
Advance Information 155
NON-DISCLOSURE
This read/write status and control bit is set when a break address match occurs. Writing a logic 1 to BRKA generates a break interrupt. Clear BRKA by writing a logic 0 to it before exiting the break routine. Reset clears the BRKA bit. 1 = Break address match 0 = No break address match
AGREEMENT
REQUIRED
Break Module (Break) REQUIRED
11.5.2 Break Address Registers The break address registers contain the high and low bytes of the desired breakpoint address. Reset clears the break address registers.
Address: $FE0C Bit 7 Read: BIT 15 Write: BIT 13 0 BIT 13 0 BIT 12 0 BIT 11 0 BIT 10 0 BIT 9 0 BIT 8 0 6 5 4 3 2 1 Bit 0
AGREEMENT
Reset:
0
Figure 11-3. Break Address Register (BRKH)
Address: $FE0D Bit 7 Read: BIT 7 Write: Reset: 0 0 0 0 0 0 0 0 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0 6 5 4 3 2 1 Bit 0
Figure 11-4. Break Address Register (BRKL)
NON-DISCLOSURE
11.6 Low-Power Modes
The WAIT and STOP instructions put the MCU in low-power standby modes.
11.6.1 Wait Mode If enabled, the break module is active in wait mode. The SIM break stop/wait bit (SBSW) in the SIM break status register indicates whether wait was exited by a break interrupt. If so, the user can modify the return address on the stack by subtracting one from it to re-execute the stop or wait opcode. (See 9.8.1 SIM Break Status Register.)
Advance Information 156 Break Module (Break)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Break Module (Break) Low-Power Modes
11.6.2 Stop Mode The break module is inactive in stop mode. The STOP instruction does not affect break module register states. A break interrupt will cause an exit from stop mode and sets the SBSW bit in the SIM break status register.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Break Module (Break)
Advance Information 157
NON-DISCLOSURE
AGREEMENT
REQUIRED
Break Module (Break) REQUIRED NON-DISCLOSURE
Advance Information 158 Break Module (Break)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 12. Monitor ROM (MON)
12.1 Contents
12.2 12.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
12.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 12.4.1 Entering Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . .162 12.4.2 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 12.4.3 Echoing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 12.4.4 Break Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 12.4.5 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165 12.4.6 Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
12.2 Introduction
This section describes the monitor ROM (MON). The monitor ROM allows complete testing of the MCU through a single-wire interface with a host computer.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Monitor ROM (MON)
Advance Information 159
NON-DISCLOSURE
AGREEMENT
REQUIRED
Monitor ROM (MON) REQUIRED 12.3 Features
Features of the monitor ROM include: * * * * * Normal user-mode pin functionality One pin dedicated to serial communication between monitor ROM and Host computer Standard mark/space non-return-to-zero (NRZ) communication with host computer 4800 Baud-28.8 kBaud communication with host computer Execution of code in RAM or ROM
AGREEMENT
12.4 Functional Description
Monitor ROM receives and executes commands from a host computer. Figure 12-1 shows a sample circuit used to enter monitor mode and communicate with a host computer via a standard RS-232 interface. While simple monitor commands can access any memory address, the MC68HC08AS32 has a ROM security feature that requires proper procedures to be followed before the ROM can be accessed. Access to the ROM is denied to unauthorized users of customer-specified software. In monitor mode, the MCU can execute host-computer code in RAM while all MCU pins except PTA0 retain normal operating mode functions. All communication between the host computer and the MCU is through the PTA0 pin. A level-shifting and multiplexing interface is required between PTA0 and the host computer. PTA0 is used in a wired-OR configuration and requires a pullup resistor.
NON-DISCLOSURE
Advance Information 160
MC68HC08AS32 -- Rev. 3.0 Monitor ROM (MON) MOTOROLA
Monitor ROM (MON) Functional Description
VDD 68HC08 10 k RST 0.1 F
VDD + VHI 10 IRQ1/VPP
VDDA
VDDA/VDDAREF CGMXFC
1 10 F + 3 4 10 F +
MC145407
20 + 18 17 + 10 F VDD 20 pF 20 pF X1 4.9152 MHz 10 F
0.1 F
OSC1 10 M OSC2
2
19
5 6
16 15 VDD VDD 0.1 F VDD 1 2 6 4 MC74HC125 14 3 5 VDD 10 k A (SEE NOTE.) VDD 10 k PTA0
3 7
PTC3 VDD 10 k PTC0 PTC1
7
NOTE: Position A -- Bus clock = CGMXCLK / 4 or CGMVCLK / 4 Position B -- Bus clock = CGMXCLK / 2
B
Figure 12-1. Monitor Mode Circuit
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Monitor ROM (MON) Advance Information 161
NON-DISCLOSURE
DB-25 2
VSS
AGREEMENT
REQUIRED
Monitor ROM (MON) REQUIRED
12.4.1 Entering Monitor Mode Table 12-1 shows the pin conditions for entering monitor mode. Table 12-1. Mode Selection
PTC0 Pin PTC1 Pin PTA0 Pin PTC3 Pin IRQ Pin Bus Frequency
Mode
CGMOUT
AGREEMENT
VDD + VHI(1) VDD + VHI(1)
1
0
1
1
Monitor
CGMXCLK CGMVCLK ---------------------------- or ---------------------------2 2
CGMOUT ------------------------2 CGMOUT ------------------------2
1
0
1
0
Monitor
CGMXCLK
1. For VHI, see 21.5 5.0-Volt DC Electrical Characteristics Control Timing and 21.2 Maximum Ratings
Enter monitor mode by either: * * Executing a software interrupt instruction (SWI) or Applying a logic 0 and then a logic 1 to the RST pin
NON-DISCLOSURE
The MCU sends a break signal (10 consecutive logic 0s) to the host computer, indicating that it is ready to receive a command. The break signal also provides a timing reference to allow the host to determine the necessary baud rate. Monitor mode uses alternate vectors for reset, SWI, and break interrupt. The alternate vectors are in the $FE page instead of the $FF page and allow code execution from the internal monitor firmware instead of user code. The COP module is disabled in monitor mode as long as VDD + VHI (see 21.5 5.0-Volt DC Electrical Characteristics Control Timing) is applied to either the IRQ pin or the VDD pin. (See Section 9. System Integration Module (SIM) for more information on modes of operation.)
NOTE:
Holding the PTC3 pin low when entering monitor mode causes a bypass of a divide-by-two stage at the oscillator. The CGMOUT frequency is equal to the CGMXCLK frequency, and the OSC1 input directly
Advance Information 162 Monitor ROM (MON)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Monitor ROM (MON) Functional Description
generates internal bus clocks. In this case, the OSC1 signal must have a 50% duty cycle at maximum bus frequency.
Table 12-2 is a summary of the differences between user mode and monitor mode. Table 12-2. Mode Differences
Functions Modes COP User Monitor Enabled Disabled(1) Reset Vector High $FFFE $FEFE Reset Vector Low $FFFF $FEFF Break Vector High $FFFC $FEFC Break Vector Low $FFFD $FEFD SWI Vector High $FFFC $FEFC SWI Vector Low $FFFD $FEFD
1. If the high voltage (VDD + VHI) is removed from the IRQ/VPP pin while in monitor mode, the SIM asserts its COP enable output. The COP is a mask option enabled or disabled by the COPD bit in the configuration register. (See 21.5 5.0-Volt DC Electrical Characteristics Control Timing.)
12.4.2 Data Format Communication with the monitor ROM is in standard non-return-to-zero (NRZ) mark/space data format. (See Figure 12-2 and Figure 12-3.) The data transmit and receive rate can be anywhere from 4800 baud to 28.8 kBaud. Transmit and receive baud rates must be identical.
START BIT
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
STOP BIT
NEXT START BIT
Figure 12-2. Monitor Data Format
$A5
START BIT START BIT
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
STOP BIT STOP BIT
NEXT START BIT
BREAK
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
BIT 6
BIT 7
NEXT START BIT
Figure 12-3. Sample Monitor Waveforms
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Monitor ROM (MON) Advance Information 163
NON-DISCLOSURE
AGREEMENT
REQUIRED
Monitor ROM (MON) REQUIRED
12.4.3 Echoing As shown in Figure 12-4, the monitor ROM immediately echoes each received byte back to the PTA0 pin for error checking. Any result of a command appears after the echo of the last byte of the command.
SENT TO MONITOR
AGREEMENT
READ
READ
ADDR. HIGH
ADDR. HIGH
ADDR. LOW
ADDR. LOW
DATA
ECHO
RESULT
Figure 12-4. Read Transaction
12.4.4 Break Signal A start bit followed by nine low bits is a break signal. (See Figure 12-5.) When the monitor receives a break signal, it drives the PTA0 pin high for the duration of two bits before echoing the break signal.
NON-DISCLOSURE
MISSING STOP BIT TWO-STOP-BIT DELAY BEFORE ZERO ECHO
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
Figure 12-5. Break Transaction
Advance Information 164 Monitor ROM (MON)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Monitor ROM (MON) Functional Description
12.4.5 Commands The monitor ROM uses these commands: * * * * * * READ, read memory WRITE, write memory IREAD, indexed read IWRITE, indexed write READSP, read stack pointer RUN, run user program
A sequence of IREAD or IWRITE commands can access a block of memory sequentially over the full 64-Kbyte memory map.
Table 12-3. READ (Read Memory) Command
Description Operand Data Returned Opcode Read byte from memory Specifies 2-byte address in high byte:low byte order Returns contents of specified address $4A
Command Sequence
SENT TO MONITOR READ READ ADDR. HIGH ADDR. HIGH ADDR. LOW ADDR. LOW DATA
ECHO
RESULT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Monitor ROM (MON)
Advance Information 165
NON-DISCLOSURE
AGREEMENT
REQUIRED
Monitor ROM (MON) REQUIRED
Table 12-4. WRITE (Write Memory) Command
Description Operand Data Returned Opcode Write byte to memory Specifies 2-byte address in high byte:low byte order; low byte followed by data byte None $49
Command Sequence
AGREEMENT
SENT TO MONITOR
WRITE
WRITE
ADDR. HIGH
ADDR. HIGH
ADDR. LOW
ADDR. LOW
DATA
DATA
ECHO
Table 12-5. IREAD (Indexed Read) Command
Description Operand Data Returned Read next 2 bytes in memory from last address accessed Specifies 2-byte address in high byte:low byte order Returns contents of next two addresses $1A
NON-DISCLOSURE
Opcode
Command Sequence
SENT TO MONITOR IREAD IREAD DATA DATA
ECHO
RESULT
Advance Information 166 Monitor ROM (MON)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Monitor ROM (MON) Functional Description
Table 12-6. IWRITE (Indexed Write) Command
Description Operand Data Returned Opcode Write to last address accessed + 1 Specifies single data byte None $19
Command Sequence
SENT TO MONITOR IWRITE IWRITE DATA DATA
ECHO
Table 12-7. READSP (Read Stack Pointer) Command
Description Operand Data Returned Opcode Reads stack pointer None Returns stack pointer in high byte:low byte order
Command Sequence
SENT TO MONITOR READSP READSP SP HIGH SP LOW
ECHO
RESULT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Monitor ROM (MON)
Advance Information 167
NON-DISCLOSURE
$0C
AGREEMENT
REQUIRED
Monitor ROM (MON) REQUIRED
Table 12-8. RUN (Run User Program) Command
Description Operand Data Returned Opcode Executes RTI instruction None None $28
Command Sequence
SENT TO MONITOR
AGREEMENT
RUN
RUN
ECHO
12.4.6 Baud Rate With a 4.9152-MHz crystal and the PTC3 pin at logic 1 during reset, data is transferred between the monitor and host at 4800 baud. If the PTC3 pin is at logic 0 during reset, the monitor baud rate is 9600. When the CGM output, CGMOUT, is driven by the PLL, the baud rate is determined by the MUL[7:4] bits in the PLL programming register (PPG). (See Section 8. Clock Generator Module (CGM).) Table 12-9. Monitor Baud Rate Selection
VCO Frequency Multiplier (N) 1 Monitor Baud Rate (4.9152 MHz) Monitor Baud Rate (4.194 MHz) 4800 4096 2 9600 8192 3 14,400 12,288 4 19,200 16,384 5 24,000 20,480 6 28,800 24,576
NON-DISCLOSURE
Advance Information 168 Monitor ROM (MON)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 13. Computer Operating Properly (COP)
13.1 Contents
13.2 13.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
13.4 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.1 CGMXCLK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.2 STOP Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.3 COPCTL Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.4 Internal Reset Resources . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.5 Reset Vector Fetch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.6 COPD (COP Disable) . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 13.4.7 COPS (COP Short Timeout) . . . . . . . . . . . . . . . . . . . . . . .173 13.5 13.6 13.7 COP Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
13.8 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 13.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 13.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 13.9 COP Module During Break Interrupts . . . . . . . . . . . . . . . . . . .174
13.2 Introduction
This section describes the computer operating properly (COP) module, a free-running counter that generates a reset if allowed to overflow. The COP module helps software recover from runaway code. Prevent a COP reset by periodically clearing the COP counter.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Computer Operating Properly (COP)
Advance Information 169
NON-DISCLOSURE
AGREEMENT
REQUIRED
Computer Operating Properly (COP) REQUIRED 13.3 Functional Description
Figure 13-1 shows the structure of the COP module.
SIM
CGMXCLK 12-BIT SIM COUNTER SIM RESET CIRCUIT SIM RESET STATUS REGISTER
CLEAR ALL BITS
AGREEMENT
STOP INSTRUCTION INTERNAL RESET SOURCES(1) RESET VECTOR FETCH COPCTL WRITE
COP MODULE
COPEN (FROM SIM) COPD (FROM MOR) RESET COPCTL WRITE 6-BIT COP COUNTER
CLEAR COP COUNTER
NON-DISCLOSURE
COPS
1. See 9.4.2 Active Resets from Internal Sources.
Figure 13-1. COP Block Diagram
Advance Information 170 Computer Operating Properly (COP)
CLEAR BITS 12-4
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Computer Operating Properly (COP) Functional Description
The COP counter is a free-running 6-bit counter preceded by the 12-bit system integration module (SIM) counter. COP timeouts are determined strictly by the CGM crystal oscillator clock signal (CGMXCLK), not the CGMOUT signal (see Figure 8-1. CGM Block Diagram). If not cleared by software, the COP counter overflows and generates an asynchronous reset after (213 - 24) or (218 - 24) CGMXCLK cycles, depending upon COPS bit in the MOR register ($001F) (See Section 5. Mask Options.) With a 4.9152-MHz crystal and the COPS bit in the MOR register ($001F) set to a logic 1, the COP timeout period is approximately 53.3 ms. Writing any value to location $FFFF before overflow occurs clears the COP counter, clears bits 12 through 4 of the SIM counter, and prevents reset. A CPU interrupt routine can be used to clear the COP.
NOTE:
The COP should be serviced as soon as possible out of reset and before entering or after exiting stop mode to guarantee the maximum selected amount of time before the first timeout.
A COP reset pulls the RST pin low for 32 CGMXCLK cycles and sets the COP bit in the SIM reset status register (SRSR) (see 9.8.2 SIM Reset Status Register). While the microcontroller is in monitor mode, the COP module is disabled if the RST pin or the IRQ pin is held at VDD + VHI (see 21.5 5.0-Volt DC Electrical Characteristics Control Timing). During a break state, VDD + VHI on the RST pin disables the COP module.
NOTE:
Place COP clearing instructions in the main program and not in an interrupt subroutine. Such an interrupt subroutine could keep the COP from generating a reset even while the main program is not working properly. The one exception to this is wait mode (see 13.8.1 Wait Mode).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Computer Operating Properly (COP)
Advance Information 171
NON-DISCLOSURE
AGREEMENT
REQUIRED
Computer Operating Properly (COP) REQUIRED 13.4 I/O Signals
The following paragraphs describe the signals shown in Figure 13-1.
13.4.1 CGMXCLK CGMXCLK is the crystal oscillator output signal. CGMXCLK frequency is equal to the crystal frequency.
AGREEMENT
13.4.2 STOP Instruction The STOP instruction clears the SIM counter.
13.4.3 COPCTL Write Writing any value to the COP control register (COPCTL) (see 13.5 COP Control Register) clears the COP counter and clears bits 12 through 4 of the SIM counter. Reading the COP control register returns the reset vector.
NON-DISCLOSURE
13.4.4 Internal Reset Resources An internal reset clears the SIM counter and the COP counter. (See 9.4.2 Active Resets from Internal Sources.)
13.4.5 Reset Vector Fetch A reset vector fetch occurs when the vector address appears on the data bus. A reset vector fetch clears the SIM counter.
13.4.6 COPD (COP Disable) The COPD bit reflects the state of the COP disable bit (COPD) in the MOR register ($001F). This signal disables COP-generated resets when asserted. (See Section 5. Mask Options.)
Advance Information 172 Computer Operating Properly (COP)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Computer Operating Properly (COP) COP Control Register
13.4.7 COPS (COP Short Timeout) The COPS bit selects the state of the COP short timeout bit (COPS) in the MOR register ($001F). Timeout periods can be (218 -24) or (213 -24) CGMXCLK cycles. (See 5.4 Mask Option Register.)
13.5 COP Control Register
The COP control register is located at address $FFFF and overlaps the reset vector. Writing any value to $FFFF clears the COP counter and starts a new timeout period. Reading location $FFFF returns the low byte of the reset vector.
Address: $FFFF Bit 7 Read: Write: Reset: 6 5 4 3 2 1 Bit 0
Low Byte of Reset Vector Clear COP Counter Unaffected by Reset
Figure 13-2. COP Control Register (COPCTL)
13.6 Interrupts
The COP does not generate CPU interrupt requests.
13.7 Monitor Mode
The COP is disabled in monitor mode when VDD + VHI (see 21.5 5.0-Volt DC Electrical Characteristics Control Timing) is present on the IRQ pin or on the RST pin.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Computer Operating Properly (COP)
Advance Information 173
NON-DISCLOSURE
AGREEMENT
REQUIRED
Computer Operating Properly (COP) REQUIRED 13.8 Low-Power Modes
The following subsections describe the low-power modes.
13.8.1 Wait Mode The COP continues to operate during wait mode. To prevent a COP reset during wait mode, periodically clear the COP counter in a CPU interrupt routine.
AGREEMENT
NOTE:
If the COP is enabled in wait mode, it must be periodically refreshed. (See 13.4.6 COPD (COP Disable).)
13.8.2 Stop Mode Stop mode turns off the CGMXCLK input to the COP and clears the SIM counter. Service the COP immediately before entering or after exiting stop mode to ensure a full COP timeout period after entering or exiting stop mode. The STOP bit in the MOR register ($001F) (see Section 5. Mask Options) enables the STOP instruction. To prevent inadvertently turning off the COP with a STOP instruction, disable the STOP instruction by programming the STOP bit to logic 0.
NON-DISCLOSURE
13.9 COP Module During Break Interrupts
The COP is disabled during a break interrupt when VDD + VHI (see 21.5 5.0-Volt DC Electrical Characteristics Control Timing) is present on the RST pin.
Advance Information 174 Computer Operating Properly (COP)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 14. External Interrupt (IRQ)
14.1 Contents
14.2 14.3 14.4 14.5 14.6 14.7 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 IRQ Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 IRQ Module During Break Interrupts . . . . . . . . . . . . . . . . . . .180 IRQ Status and Control Register . . . . . . . . . . . . . . . . . . . . . .180
14.2 Introduction
This section describes the non-maskable external interrupt (IRQ) input.
14.3 Features
Features of the IRQ include: * * * * Dedicated external interrupt pin (IRQ) Hysteresis buffer Programmable edge-only or edge and level interrupt sensitivity Automatic interrupt acknowledge
MC68HC08AS32 -- Rev. 3.0 MOTOROLA External Interrupt (IRQ)
Advance Information 175
NON-DISCLOSURE
AGREEMENT
REQUIRED
External Interrupt (IRQ) REQUIRED 14.4 Functional Description
A logic 0 applied to the external interrupt pin can latch a CPU interrupt request. Figure 14-1 shows the structure of the IRQ module. Interrupt signals on the IRQ pin are latched into the IRQ latch. An interrupt latch remains set until one of the following actions occurs: * Vector fetch -- A vector fetch automatically generates an interrupt acknowledge signal that clears the latch that caused the vector fetch. Software clear -- Software can clear an interrupt latch by writing to the appropriate acknowledge bit in the interrupt status and control register (ISCR). Writing a logic 1 to the ACK bit clears the IRQ latch. Reset -- A reset automatically clears both interrupt latches.
AGREEMENT
*
*
ACK INTERNAL ADDRESS BUS TO CPU FOR BIL/BIH INSTRUCTIONS
VECTOR FETCH DECODER
NON-DISCLOSURE
VDD D IRQ CLR Q SYNCHRONIZER
IRQF
CK IRQ LATCH IMASK
IRQ INTERRUPT REQUEST
MODE HIGH VOLTAGE DETECT TO MODE SELECT LOGIC
Figure 14-1. IRQ Block Diagram
Advance Information 176 External Interrupt (IRQ)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
External Interrupt (IRQ) Functional Description
Table 14-1. IRQ I/O Register Summary
Addr. $001A Register Name Read: IRQ Status/Control Register (ISCR) Write: R R R R R ACK Bit 7 0 6 0 5 0 4 0 3 IRQF 2 0 IMASK MODE 1 Bit 0
R
= Reserved
When an interrupt pin is edge-triggered only, the interrupt latch remains set until a vector fetch, software clear, or reset occurs. When an interrupt pin is both falling-edge and low-level triggered, the interrupt latch remains set until both of the following occur: * * Vector fetch or software clear Return of the interrupt pin to logic 1
When set, the IMASK bit in the ISCR masks all external interrupt requests. A latched interrupt request is not presented to the interrupt priority logic unless the corresponding IMASK bit is clear.
NOTE:
The interrupt mask (I) in the condition code register (CCR) masks all interrupt requests, including external interrupt requests. (See Figure 14-2.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA External Interrupt (IRQ)
Advance Information 177
NON-DISCLOSURE
The vector fetch or software clear may occur before or after the interrupt pin returns to logic 1. As long as the pin is low, the interrupt request remains pending. A reset will clear the latch and the MODE control bit, thereby clearing the interrupt even if the pin stays low.
AGREEMENT
The external interrupt pin is falling-edge triggered and is softwareconfigurable to be both falling-edge and low-level triggered. The MODE bit in the ISCR controls the triggering sensitivity of the IRQ pin.
REQUIRED
External Interrupt (IRQ) REQUIRED
FROM RESET
YES
I BIT SET?
NO
INTERRUPT?
YES
AGREEMENT
NO STACK CPU REGISTERS SET I BIT LOAD PC WITH INTERRUPT VECTOR
FETCH NEXT INSTRUCTION.
SWI INSTRUCTION? NO
YES
NON-DISCLOSURE
RTI INSTRUCTION? NO
YES
UNSTACK CPU REGISTERS
EXECUTE INSTRUCTION
Figure 14-2. IRQ Interrupt Flowchart
Advance Information 178 External Interrupt (IRQ)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
External Interrupt (IRQ) IRQ Pin
14.5 IRQ Pin
A logic 0 on the IRQ pin can latch an interrupt request into the IRQ latch. A vector fetch, software clear, or reset clears the IRQ latch. If the MODE bit is set, the IRQ pin is both falling-edge sensitive and low-level sensitive. With MODE set, both of the following actions must occur to clear the IRQ latch: * Vector fetch or software clear -- A vector fetch generates an interrupt acknowledge signal to clear the latch. Software may generate the interrupt acknowledge signal by writing a logic 1 to the ACK bit in the interrupt status and control register (ISCR). The ACK bit is useful in applications that poll the IRQ pin and require software to clear the IRQ latch. Writing to the ACK bit can also prevent spurious interrupts due to noise. Setting ACK does not affect subsequent transitions on the IRQ pin. A falling edge on IRQ that occurs after writing to the ACK bit latches another interrupt request. If the IRQ mask bit, IMASK, is clear, the CPU loads the program counter with the vector address at locations $FFFA and $FFFB. Return of the IRQ pin to logic 1 -- As long as the IRQ pin is at logic 0, the IRQ latch remains set.
*
The vector fetch or software clear and the return of the IRQ pin to logic 1 can occur in any order. The interrupt request remains pending as long as the IRQ pin is at logic 0. A reset will clear the latch and the MODE control bit, thereby clearing the interrupt even if the pin stays low. If the MODE bit is clear, the IRQ pin is falling-edge sensitive only. With MODE clear, a vector fetch or software clear immediately clears the IRQ latch.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA External Interrupt (IRQ)
Advance Information 179
NON-DISCLOSURE
AGREEMENT
REQUIRED
External Interrupt (IRQ) REQUIRED
The IRQF bit in the ISCR register can be used to check for pending interrupts. The IRQF bit is not affected by the IMASK bit, which makes it useful in applications where polling is preferred. Use the BIH or BIL instruction to read the logic level on the IRQ pin.
NOTE:
When using the level-sensitive interrupt trigger, avoid false interrupts by masking interrupt requests in the interrupt routine.
AGREEMENT
14.6 IRQ Module During Break Interrupts
The system integration module (SIM) controls whether the IRQ interrupt latch can be cleared during the break state. The BCFE bit in the SIM break flag control register (SBFCR) enables software to clear the latches during the break state. (See 9.8.3 SIM Break Flag Control Register.) To allow software to clear the IRQ latch during a break interrupt, write a logic 1 to the BCFE bit. If a latch is cleared during the break state, it remains cleared when the MCU exits the break state. To protect the latch during the break state, write a logic 0 to the BCFE bit. With BCFE at logic 0 (its default state), writing to the ACK bit in the IRQ status and control register during the break state has no effect on the IRQ latch.
NON-DISCLOSURE
14.7 IRQ Status and Control Register
The IRQ status and control register (ISCR) controls and monitors operation of the IRQ module. The ISCR: * * * * Shows the state of the IRQ interrupt flag Clears the IRQ interrupt latch Masks IRQ interrupt request Controls triggering sensitivity of the IRQ interrupt pin
Advance Information 180 External Interrupt (IRQ)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
External Interrupt (IRQ) IRQ Status and Control Register
Address:
$001A Bit 7 6 0 R 0 = Reserved 5 0 R 0 4 0 R 0 3 IRQF R 0 2 0 IMASK MODE 0 ACK 0 0 1 Bit 0
Read: Write: Reset:
0 R 0 R
Figure 14-3. IRQ Status and Control Register (ISCR) IRQF -- IRQ Flag Bit This read-only status bit is high when the IRQ interrupt is pending. 1 = IRQ interrupt pending 0 = IRQ interrupt not pending ACK -- IRQ Interrupt Request Acknowledge Bit Writing a logic 1 to this write-only bit clears the IRQ latch. ACK always reads as logic 0. Reset clears ACK. IMASK -- IRQ Interrupt Mask Bit Writing a logic 1 to this read/write bit disables IRQ interrupt requests. Reset clears IMASK. 1 = IRQ interrupt requests disabled 0 = IRQ interrupt requests enabled MODE -- IRQ Edge/Level Select Bit This read/write bit controls the triggering sensitivity of the IRQ pin. Reset clears MODE. 1 = IRQ interrupt requests on falling edges and low levels 0 = IRQ interrupt requests on falling edges only
MC68HC08AS32 -- Rev. 3.0 MOTOROLA External Interrupt (IRQ)
Advance Information 181
NON-DISCLOSURE
AGREEMENT
REQUIRED
External Interrupt (IRQ) REQUIRED NON-DISCLOSURE
Advance Information 182 External Interrupt (IRQ)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 15. Input/Output (I/O) Ports
15.1 Contents
15.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
15.3 Port A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 15.3.1 Port A Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 15.3.2 Data Direction Register A . . . . . . . . . . . . . . . . . . . . . . . . .186 15.4 Port B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 15.4.1 Port B Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 15.4.2 Data Direction Register B . . . . . . . . . . . . . . . . . . . . . . . . .189 15.5 Port C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 15.5.1 Port C Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 15.5.2 Data Direction Register C . . . . . . . . . . . . . . . . . . . . . . . . .192 15.6 Port D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 15.6.1 Port D Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 15.6.2 Data Direction Register D . . . . . . . . . . . . . . . . . . . . . . . . .195 15.7 Port E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 15.7.1 Port E Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 15.7.2 Data Direction Register E . . . . . . . . . . . . . . . . . . . . . . . . .199 15.8 Port F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 15.8.1 Port F Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201 15.8.2 Data Direction Register F . . . . . . . . . . . . . . . . . . . . . . . . .202
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 183
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED 15.2 Introduction
Forty bidirectional input/output (I/O) pins form six parallel ports. All I/O pins are programmable as inputs or outputs.
NOTE:
Connect any unused I/O pins to an appropriate logic level, either VDD or VSS. Although the I/O ports do not require termination for proper operation, termination reduces excess current consumption and the possibility of electrostatic damage.
AGREEMENT
Table 15-1. I/O Port Register Summary
Addr. $0000 $0001 $0002 $0003 $0004 $0005 $0006 $0007 $0008 $0009 $000C $000D Register Name Port A Data Register (PTA) Port B Data Register (PTB) Port C Data Register (PTC) Port D Data Register (PTD) Bit 7 PTA7 PTB7 0 0 6 PTA6 PTB6 0 PTD6 5 PTA5 PTB5 0 PTD5 4 PTA4 PTB4 PTC4 PTD4 3 PTA3 PTB3 PTC3 PTD3 2 PTA2 PTB2 PTC2 PTD2 1 PTA1 PTB1 PTC1 PTD1 Bit 0 PTA0 PTB0 PTC0 PTD0
Data Direction Register A (DDRA) DDRA7 Data Direction Register B (DDRB) DDRB7 Data Direction Register C (DDRC) MCLKEN Data Direction Register D (DDRD) Port E Data Register (PTE) Port F Data Register (PTF) 0 PTE7 0
DDRA6 DDRA5 DDRA4 DDRA3 DDRA2 DDRA1 DDRA0 DDRB6 DDRB5 DDRB4 DDRB3 DDRB2 DDRB1 DDRB0 0 0 DDRC4 DDRC3 DDRC2 DDRC1 DDRC0
NON-DISCLOSURE
DDRD6 DDRD5 DDRD4 DDRD3 DDRD2 DDRD1 DDRD0 PTE6 0 PTE5 0 PTE4 0 PTE3 PTF3 PTE2 PTF2 PTE1 PTF1 PTE0 PTF0
Data Direction Register E (DDRE) DDRE7 Data Direction Register F (DDRF) 0
DDRE6 DDRE5 DDRE4 DDRE3 DDRE2 DDRE1 DDRE0 0 0 0 DDRF3 DDRF2 DDRF1 DDRF0
Advance Information 184 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port A
15.3 Port A
Port A is an 8-bit general-purpose bidirectional I/O port.
15.3.1 Port A Data Register The port A data register contains a data latch for each of the eight port A pins.
Address: $0000 Bit 7 Read: PTA7 Write: Reset: Unaffected by Reset PTA6 PTA5 PTA4 PTA3 PTA2 PTA1 PTA0 6 5 4 3 2 1 Bit 0
Figure 15-1. Port A Data Register (PTA) PTA[7:0] -- Port A Data Bits These read/write bits are software programmable. Data direction of each port A pin is under the control of the corresponding bit in data direction register A. Reset has no effect on port A data.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 185
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
15.3.2 Data Direction Register A Data direction register A determines whether each port A pin is an input or an output. Writing a logic 1 to a DDRA bit enables the output buffer for the corresponding port A pin; a logic 0 disables the output buffer.
Address: $0004 Bit 7 Read: DDRA7 Write: Reset: Unaffected by Reset 6 DDRA6 5 DDRA5 4 DDRA4 3 DDRA3 2 DDRA2 1 DDRA1 Bit 0 DDRA0
AGREEMENT
Figure 15-2. Data Direction Register A (DDRA) DDRA[7:0] -- Data Direction Register A Bits These read/write bits control port A data direction. Reset clears DDRA[7:0], configuring all port A pins as inputs. 1 = Corresponding port A pin configured as output 0 = Corresponding port A pin configured as input
NOTE:
NON-DISCLOSURE
Avoid glitches on port A pins by writing to the port A data register before changing data direction register A bits from 0 to 1.
Figure 15-3 shows the port A I/O logic.
READ DDRA ($0004)
WRITE DDRA ($0004) INTERNAL DATA BUS RESET WRITE PTA ($0000) PTAx PTAx DDRAx
READ PTA ($0000)
Figure 15-3. Port A I/O Circuit
Advance Information 186 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port A
When bit DDRAx is a logic 1, reading address $0000 reads the PTAx data latch. When bit DDRAx is a logic 0, reading address $0000 reads the voltage level on the pin. The data latch can always be written, regardless of the state of its data direction bit. Table 15-2 summarizes the operation of the port A pins. Table 15-2. Port A Pin Functions
DDRA Bit 0 1 PTA Bit X X I/O Pin Mode Input, Hi-Z Output Accesses to DDRA Read/Write DDRA[7:0] DDRA[7:0] Accesses to PTA Read Pin PTA[7:0] Write PTA[7:0](1) PTA[7:0]
X = Don't Care Hi-Z = High Impedance 1. Writing affects data register, but does not affect input.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 187
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED 15.4 Port B
Port B is an 8-bit special-function port that shares all of its pins with the analog-to-digital converter (ADC).
15.4.1 Port B Data Register The port B data register contains a data latch for each of the eight port B pins.
Address: $0001 Bit 7 Read: PTB7 Write: Reset: Alternate Functions: ATD7 ATD6 ATD5 Unaffected by Reset ATD4 ATD3 ATD2 ATD1 ATD0 PTB6 PTB5 PTB4 PTB3 PTB2 PTB1 PTB0 6 5 4 3 2 1 Bit 0
AGREEMENT
Figure 15-4. Port B Data Register (PTB) PTB[7:0] -- Port B Data Bits
NON-DISCLOSURE
These read/write bits are software programmable. Data direction of each port B pin is under the control of the corresponding bit in data direction register B. Reset has no effect on port B data. ATD[7:0] -- ADC Channels PTB7/ATD7-PTB0/ATD0 are eight of the 15 analog-to-digital converter channels. The ADC channel select bits, CH[4:0], determine whether the PTB7/ATD7-PTB0/ATD0 pins are ADC channels or general-purpose I/O pins. If an ADC channel is selected and a read of this corresponding bit in the port B data register occurs, the data will be 0 if the data direction for this bit is programmed as an input. Otherwise, the data will reflect the value in the data latch. (See Section 19. Analog-to-Digital Converter (ADC).) Data direction register B (DDRB) does not affect the data direction of port B pins that are being used by the ADC. However, the DDRB bits always determine whether reading port B returns to the states of the latches or logic 0.
Advance Information 188 Input/Output (I/O) Ports MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port B
15.4.2 Data Direction Register B Data direction register B determines whether each port B pin is an input or an output. Writing a logic 1 to a DDRB bit enables the output buffer for the corresponding port B pin; a logic 0 disables the output buffer.
Address: $0005 Bit 7 Read: DDRB7 Write: Reset: 0 0 0 0 0 0 0 0 DDRB6 DDRB5 DDRB4 DDRB3 DDRB2 DDRB1 DDRB0 6 5 4 3 2 1 Bit 0
Figure 15-5. Data Direction Register B (DDRB) DDRB[7:0] -- Data Direction Register B Bits These read/write bits control port B data direction. Reset clears DDRB[7:0], configuring all port B pins as inputs. 1 = Corresponding port B pin configured as output 0 = Corresponding port B pin configured as input
NOTE:
Avoid glitches on port B pins by writing to the port B data register before changing data direction register B bits from 0 to 1.
Figure 15-6 shows the port B I/O logic.
READ DDRB ($0005)
WRITE DDRB ($0005) INTERNAL DATA BUS RESET WRITE PTB ($0001) PTBx PTBx DDRBx
READ PTB ($0001)
Figure 15-6. Port B I/O Circuit
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 189
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
When bit DDRBx is a logic 1, reading address $0001 reads the PTBx data latch. When bit DDRBx is a logic 0, reading address $0001 reads the voltage level on the pin, or logic 0 if that particular bit is in use by the ADC. The data latch can always be written, regardless of the state of its data direction bit. Table 15-3 summarizes the operation of the port B pins. Table 15-3. Port B Pin Functions
DDRB Bit 0 1 0 1 PTB Bit X X X X Bit in Use by ADC No No Yes Yes I/O Pin Mode Input, Hi-Z Output Input, Hi-Z Input, Hi-Z Accesses to DDRB Read/Write DDRB[7:0] DDRB[7:0] DDRB[7:0] DDRB[7:0] Accesses to PTB Read Pin PTB[7:0] 0 PTB[7:0] Write PTB[7:0](1) PTB[7:0] PTB[7:0](1) PTB[7:0]
AGREEMENT
X = Don't Care Hi-Z = High Impedance 1. Writing affects data register, but does not affect input.
NON-DISCLOSURE
Advance Information 190 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port C
15.5 Port C
Port C is a 5-bit general-purpose bidirectional I/O port that shares one of its pins with the bus clock (MCLK).
15.5.1 Port C Data Register The port C data register contains a data latch for each of the five port C pins.
Address: $0002 Bit 7 Read: Write: Reset: R Alternate Functions: = Reserved MCLK 0 R 6 0 R 5 0 PTC4 R Unaffected by Reset PTC3 PTC2 PTC1 PTC0 4 3 2 1 Bit 0
Figure 15-7. Port C Data Register (PTC) PTC[4:0] -- Port C Data Bits These read/write bits are software-programmable. Data direction of each port C pin is under the control of the corresponding bit in data direction register C. Reset has no effect on port C data. MCLK -- T12 System Bus Clock Bit The bus clock (MCLK) is driven out of PTC2 when enabled by the MCLKEN bit in PTCDDR7.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 191
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
15.5.2 Data Direction Register C Data direction register C determines whether each port C pin is an input or an output. Writing a logic 1 to a DDRC bit enables the output buffer for the corresponding port C pin; a logic 0 disables the output buffer.
Address: $0006 Bit 7 Read: MCLKEN Write: Reset: 0 R R 0 = Reserved R 0 0 0 0 0 0 6 0 5 0 DDRC4 DDRC3 DDRC2 DDRC1 DDRC0 4 3 2 1 Bit 0
AGREEMENT
Figure 15-8. Data Direction Register C (DDRC) MCLKEN -- MCLK Enable Bit This read/write bit enables MCLK to be an output signal on PTC2. If MCLK is enabled, PTC2 is under the control of MCLKEN. Reset clears this bit. 1 = MCLK output enabled 0 = MCLK output disabled DDRC[4:0] -- Data Direction Register C Bits These read/write bits control port C data direction. Reset clears DDRC[7:0], configuring all port C pins as inputs. 1 = Corresponding port C pin configured as output 0 = Corresponding port C pin configured as input
NON-DISCLOSURE
NOTE:
Avoid glitches on port C pins by writing to the port C data register before changing data direction register C bits from 0 to 1.
Figure 15-9 shows the port C I/O logic.
Advance Information 192 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port C
READ DDRC ($0006)
WRITE DDRC ($0006) INTERNAL DATA BUS RESET WRITE PTC ($0002) PTCx PTCx DDRCx
READ PTC ($0002)
Figure 15-9. Port C I/O Circuit When bit DDRCx is a logic 1, reading address $0002 reads the PTCx data latch. When bit DDRCx is a logic 0, reading address $0002 reads the voltage level on the pin. The data latch can always be written, regardless of the state of its data direction bit. Table 15-4 summarizes the operation of the port C pins. Table 15-4. Port C Pin Functions
DDRC Bit [7] = 0 [7] = 1 0 1 PTC Bit PTC2 PTC2 X X I/O Pin Mode Input, Hi-Z Output, MCLK Input, Hi-Z Output Accesses to DDRC Read/Write DDRC[7] DDRC[7] DDRC[4:0] DDRC[4:0] Accesses to PTC Read 0 Data Latch Pin PTC[4:0] Write PTC2 -- PTC[4:3, 1:0](1) PTC[4:3, 1:0]
X = Don't Care Hi-Z = High Impedance 1. Writing affects data register, but does not affect input.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 193
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED 15.6 Port D
Port D is an 8-bit special-function I/O port that shares all of its pins with the analog-to-digital converter (ADC).
15.6.1 Port D Data Register The port D data register contains a data latch for the seven port D pins.
Address: $0003 Bit 7 Read: Write: Reset: Alternate Functions: R ATD14/ TCLK ATD13 0 PTD6 R Unaffected by Reset ATD12 ATD11 ATD10 ATD9 ATD8 PTD5 PTD4 PTD3 PTD2 PTD1 PTD0 6 5 4 3 2 1 Bit 0
AGREEMENT
R
= Reserved
Figure 15-10. Port D Data Register (PTD) PTD[6:0] -- Port D Data Bits PTD[6:0] are read/write, software programmable bits. Data direction of PTD[6:0] pins are under the control of the corresponding bit in data direction register D. ATD[14:8] -- ADC Channel Status Bits PTD6/ATD14/TCLK-PTD0/ATD8 are seven of the 15 analog-to-digital converter channels. The ADC channel select bits, CH[4:0], determine whether the PTD6/ATD14/TCLK-PTD0/ATD8 pins are ADC channels or general-purpose I/O pins. If an ADC channel is selected and a read of this corresponding bit in the port B data register occurs, the data will be 0 if the data direction for this bit is programmed as an input. Otherwise, the data will reflect the value in the data latch. (See Section 19. Analog-to-Digital Converter (ADC).)
NON-DISCLOSURE
Advance Information 194
MC68HC08AS32 -- Rev. 3.0 Input/Output (I/O) Ports MOTOROLA
Input/Output (I/O) Ports Port D
NOTE:
Data direction register D (DDRD) does not affect the data direction of port D pins that are being used by the ADC. However, the DDRD bits always determine whether reading port D returns the states of the latches or logic 0.
TCLK -- Timer Clock Input Bit The PTD6/ATD14/TCLK pin is the external clock input for the TIM. The prescaler select bits, PS[2:0], select PTD6/ATD14/TCLK as the TIM clock input. (See 16.9.1 TIM Status and Control Register.) When not selected as the TIM clock, PTD6/ATD14/TCLK is available for general-purpose I/O or as an ADC channel.
NOTE:
Do not use ADC channel ATD14 when using the PTD6/ATD14/TCLK pin as the clock input for the TIM.
15.6.2 Data Direction Register D Data direction register D determines whether each port D pin is an input or an output. Writing a logic 1 to a DDRD bit enables the output buffer for the corresponding port D pin; a logic 0 disables the output buffer.
Address: $0007 Bit 7 Read: Write: Reset: 0 DDRD6 0 0 0 0 0 0 0 0 0 DDRD5 DDRD4 DDRD3 DDRD2 DDRD1 DDRD0 6 5 4 3 2 1 Bit 0
Figure 15-11. Data Direction Register D (DDRD) DDRD[6:0] -- Data Direction Register D Bits These read/write bits control port D data direction. Reset clears DDRD[6:0], configuring all port D pins as inputs. 1 = Corresponding port D pin configured as output 0 = Corresponding port D pin configured as input
NOTE:
Avoid glitches on port D pins by writing to the port D data register before changing data direction register D bits from 0 to 1.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 195
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
Figure 15-12 shows the port D I/O logic.
READ DDRD ($0007)
WRITE DDRD ($0007) INTERNAL DATA BUS RESET WRITE PTD ($0003) PTDx PTDx DDRDx
AGREEMENT
READ PTD ($0003)
Figure 15-12. Port D I/O Circuit When bit DDRDx is a logic 1, reading address $0003 reads the PTDx data latch. When bit DDRDx is a logic 0, reading address $0003 reads the voltage level on the pin. The data latch can always be written, regardless of the state of its data direction bit. Table 15-5 summarizes the operation of the port D pins. Table 15-5. Port D Pin Functions
NON-DISCLOSURE
DDRD Bit 0 1 0 1
PTD Bit X X X X
Bit in Use by ADC No No Yes Yes
I/O Pin Mode Input, Hi-Z Output Input, Hi-Z Input, Hi-Z
Accesses to DDRD Read/Write DDRD[6:0] DDRD[6:0] DDRD[6:0] DDRD[6:0]
Accesses to PTD Read Pin PTD[6:0] 0 PTD[6:0] Write PTD[6:0](1) PTD[6:0] PTD[6:0](1) PTD[6:0]
X = Don't Care Hi-Z = High Impedance 1. Writing affects data register, but does not affect input.
Advance Information 196 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port E
15.7 Port E
Port E is an 8-bit special-function port that shares two of its pins with the timer interface module (TIM), two of its pins with the serial communications interface module (SCI), and four of its pins with the serial peripheral interface module (SPI).
15.7.1 Port E Data Register The port E data register contains a data latch for each of the eight port E pins.
Address: $0008 Bit 7 Read: PTE7 Write: Reset: Alternate Function: SPSCK MOSI MISO Unaffected by Reset SS TCH1 TCH0 RxD TxD PTE6 PTE5 PTE4 PTE3 PTE2 PTE1 PTE0 6 5 4 3 2 1 Bit 0
Figure 15-13. Port E Data Register (PTE) PTE[7:0] -- Port E Data Bits PTE[7:0] are read/write, software programmable bits. Data direction of each port E pin is under the control of the corresponding bit in data direction register E. SPSCK -- SPI Serial Clock Bit The PTE7/SPSCK pin is the serial clock input of an SPI slave module and serial clock output of an SPI master module. When the SPE bit is clear, the PTE7/SPSCK pin is available for general-purpose I/O. MOSI -- Master Out/Slave In Bit The PTE6/MOSI pin is the master out/slave in terminal of the SPI module. When the SPE bit is clear, the PTE6/MOSI pin is available for general-purpose I/O. (See 18.14.1 SPI Control Register.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 197
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
MISO -- Master In/Slave Out Bit The PTE5/MISO pin is the master in/slave out terminal of the SPI module. When the SPI enable bit, SPE, is clear, the SPI module is disabled, and the PTE5/MISO pin is available for general-purpose I/O. (See 18.14.1 SPI Control Register.) SS -- Slave Select Bit The PTE4/SS pin is the slave select input of the SPI module. When the SPE bit is clear or when the SPI master bit, SPMSTR, is set and MODFEN bit is low, the PTE4/SS pin is available for general-purpose I/O. (See 18.13.4 SS (Slave Select).) When the SPI is enabled as a slave, the DDRE4 bit in data direction register E (DDRE) has no effect on the PTE4/SS pin.
AGREEMENT
NOTE:
Data direction register E (DDRE) does not affect the data direction of port E pins that are being used by the SPI module. However, the DDRE bits always determine whether reading port E returns the states of the latches or the states of the pins. (See Table 15-6.)
TCH[1:0] -- Timer Channel I/O Bits The PTE3/TCH1-PTE2/TCH0 pins are the TIM input capture/output compare pins. The edge/level select bits, ELSxB:ELSxA, determine whether the PTE3/TCH1-PTE2/TCH0 pins are timer channel I/O pins or general-purpose I/O pins. (See 16.9.4 TIM Channel Status and Control Registers.)
NON-DISCLOSURE
NOTE:
Data direction register E (DDRE) does not affect the data direction of port E pins that are being used by the TIM. However, the DDRE bits always determine whether reading port E returns the states of the latches or the states of the pins. (See Table 15-6.)
RxD -- SCI Receive Data Input Bit The PTE1/RxD pin is the receive data input for the SCI module. When the enable SCI bit, ENSCI, is clear, the SCI module is disabled, and the PTE1/RxD pin is available for general-purpose I/O. (See 17.9.1 SCI Control Register 1.)
Advance Information 198 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port E
TxD -- SCI Transmit Data Output The PTE0/TxD pin is the transmit data output for the SCI module. When the enable SCI bit, ENSCI, is clear, the SCI module is disabled, and the PTE0/TxD pin is available for general-purpose I/O. (See 17.9.1 SCI Control Register 1.)
NOTE:
Data direction register E (DDRE) does not affect the data direction of port E pins that are being used by the SCI module. However, the DDRE bits always determine whether reading port E returns the states of the latches or the states of the pins. (See Table 15-6.)
15.7.2 Data Direction Register E Data direction register E determines whether each port E pin is an input or an output. Writing a logic 1 to a DDRE bit enables the output buffer for the corresponding port E pin; a logic 0 disables the output buffer.
Address: $000C Bit 7 Read: DDRE7 Write: Reset: 0 0 0 0 0 0 0 0 DDRE6 DDRE5 DDRE4 DDRE3 DDRE2 DDRE1 DDRE0 6 5 4 3 2 1 Bit 0
Figure 15-14. Data Direction Register E (DDRE) DDRE[7:0] -- Data Direction Register E Bits These read/write bits control port E data direction. Reset clears DDRE[7:0], configuring all port E pins as inputs. 1 = Corresponding port E pin configured as output 0 = Corresponding port E pin configured as input
NOTE:
Avoid glitches on port E pins by writing to the port E data register before changing data direction register E bits from 0 to 1.
Figure 15-15 shows the port E I/O logic.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 199
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
READ DDRE ($000C)
WRITE DDRE ($000C) INTERNAL DATA BUS RESET WRITE PTE ($0008) PTEx PTEx DDREx
READ PTE ($0008)
AGREEMENT
Figure 15-15. Port E I/O Circuit When bit DDREx is a logic 1, reading address $0008 reads the PTEx data latch. When bit DDREx is a logic 0, reading address $0008 reads the voltage level on the pin. The data latch can always be written, regardless of the state of its data direction bit. Table 15-6 summarizes the operation of the port E pins. Table 15-6. Port E Pin Functions
DDRE Bit PTE Bit X X I/O Pin Mode Input, Hi-Z Output Accesses to DDRE Read/Write 0 1 DDRE[7:0] DDRE[7:0] Accesses to PTE Read Pin PTE[7:0] Write PTE[7:0](1) PTE[7:0]
NON-DISCLOSURE
X = Don't Care Hi-Z = High Impedance 1. Writing affects data register, but does not affect input.
Advance Information 200 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port F
15.8 Port F
Port F is a 4-bit special-function port that shares four of its pins with the timer interface module (TIM).
15.8.1 Port F Data Register The port F data register contains a data latch for each of the four port F pins.
Address: $0009 Bit 7 Read: Write: Reset: Alternate Function: R = Reserved 0 R 6 0 R 5 0 R 4 0 PTF3 R Unaffected by Reset TCH5 TCH4 TCH3 TCH2 PTF2 PTF1 PTF0 3 2 1 Bit 0
Figure 15-16. Data Direction Register F (DDRF) PTF[3:0] -- Port F Data Bits These read/write bits are software programmable. Data direction of each port F pin is under the control of the corresponding bit in data direction register F. Reset has no effect on PTF[3:0]. TCH[5:2] -- Timer Channel I/O Bits The PTF3/TCH5-PTF0/TCH2 pins are the TIM input capture/output compare pins. The edge/level select bits, ELSxB-ELSxA, determine whether the PTF3/TCH5-PTF0/TCH2 pins are timer channel I/O pins or general-purpose I/O pins. (See 16.9.4 TIM Channel Status and Control Registers.)
NOTE:
Data direction register F (DDRF) does not affect the data direction of port F pins that are being used by the TIM. However, the DDRF bits always determine whether reading port F returns the states of the latches or the states of the pins. (See Table 15-7.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 201
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED
15.8.2 Data Direction Register F Data direction register F determines whether each port F pin is an input or an output. Writing a logic 1 to a DDRF bit enables the output buffer for the corresponding port F pin; a logic 0 disables the output buffer.
Address: $000D Bit 7 Read: 0 R 0 R 6 0 R 0 = Reserved 5 0 R 0 4 0 DDRF3 Write: Reset: R 0 0 0 0 0 DDRF2 DDRF1 DDRF0 3 2 1 Bit 0
AGREEMENT
Figure 15-17. Data Direction Register F (DDRF) DDRF[3:0] -- Data Direction Register F Bits These read/write bits control port F data direction. Reset clears DDRF[3:0], configuring all port F pins as inputs. 1 = Corresponding port F pin configured as output 0 = Corresponding port F pin configured as input
NON-DISCLOSURE
NOTE:
Avoid glitches on port F pins by writing to the port F data register before changing data direction register F bits from 0 to 1.
Figure 15-18 shows the port F I/O logic.
READ DDRF ($000D)
WRITE DDRF ($000D) INTERNAL DATA BUS RESET WRITE PTF ($0009) PTFx PTFx DDRFx
READ PTF ($0009)
Figure 15-18. Port F I/O Circuit
Advance Information 202 Input/Output (I/O) Ports
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Input/Output (I/O) Ports Port F
When bit DDRFx is a logic 1, reading address $0009 reads the PTFx data latch. When bit DDRFx is a logic 0, reading address $0009 reads the voltage level on the pin. The data latch can always be written, regardless of the state of its data direction bit. Table 15-7 summarizes the operation of the port F pins. Table 15-7. Port F Pin Functions
DDRF Bit 0 1 PTF Bit X X I/O Pin Mode Input, Hi-Z Output Accesses to DDRF Read/Write DDRF[3:0] DDRF[3:0] Accesses to PTF Read Pin PTF[3:0] Write PTF[3:0](1) PTF[3:0]
X = Don't Care Hi-Z = High Impedance 1. Writing affects data register, but does not affect input.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Input/Output (I/O) Ports
Advance Information 203
NON-DISCLOSURE
AGREEMENT
REQUIRED
Input/Output (I/O) Ports REQUIRED NON-DISCLOSURE
Advance Information 204 Input/Output (I/O) Ports
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 16. Timer Interface (TIM)
16.1 Contents
16.2 16.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
16.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209 16.4.1 TIM Counter Prescaler . . . . . . . . . . . . . . . . . . . . . . . . . . .209 16.4.2 Input Capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209 16.4.3 Output Compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211 16.4.3.1 Unbuffered Output Compare . . . . . . . . . . . . . . . . . . . . .211 16.4.3.2 Buffered Output Compare . . . . . . . . . . . . . . . . . . . . . . .212 16.4.4 Pulse Width Modulation (PWM) . . . . . . . . . . . . . . . . . . . .213 16.4.4.1 Unbuffered PWM Signal Generation . . . . . . . . . . . . . . .214 16.4.4.2 Buffered PWM Signal Generation . . . . . . . . . . . . . . . . .215 16.4.4.3 PWM Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216 16.5 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
16.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218 16.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218 16.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219 16.7 TIM During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . .219
16.8 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220 16.8.1 TIM Clock Pin (PTD6/ATD14/TCLK) . . . . . . . . . . . . . . . . .220 16.8.2 TIM Channel I/O Pins (PTF3/TCH5-PTF0/TCH2 and PTE3/TCH1-PTE2/TCH0) . . . . . . . . . . . . . . . . . .220 16.9 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 16.9.1 TIM Status and Control Register . . . . . . . . . . . . . . . . . . . .221 16.9.2 TIM Counter Registers . . . . . . . . . . . . . . . . . . . . . . . . . . .224 16.9.3 TIM Counter Modulo Registers . . . . . . . . . . . . . . . . . . . . .225 16.9.4 TIM Channel Status and Control Registers. . . . . . . . . . . .226 16.9.5 TIM Channel Registers . . . . . . . . . . . . . . . . . . . . . . . . . . .231
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM) Advance Information 205
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED 16.2 Introduction
This section describes the timer interface module (TIM6). The TIM is a 6-channel timer that provides a timing reference with input capture, output compare, and pulse-width-modulation functions. Figure 16-1 is a block diagram of the TIM.
16.3 Features AGREEMENT
Features of the TIM include: * Six input capture/output compare channels: - Rising-edge, falling-edge, or any-edge input capture trigger - Set, clear, or toggle output compare action * * Buffered and unbuffered pulse width modulation (PWM) signal generation Programmable TIM clock input - 7-frequency internal bus clock prescaler selection - External TIM clock input (4-MHz maximum frequency) * * * * Free-running or modulo up-count operation Toggle any channel pin on overflow TIM counter stop and reset bits Modular architecture expandable to eight channels
NON-DISCLOSURE
Advance Information 206
MC68HC08AS32 -- Rev. 3.0 Timer Interface (TIM) MOTOROLA
Timer Interface (TIM) Features
PTD6/ATD14/TCLK INTERNAL BUS CLOCK TSTOP TRST 16-BIT COUNTER
TCLK PRESCALER SELECT PRESCALER
PS2
PS1
PS0
TOF TOIE
INTERRUPT LOGIC
16-BIT COMPARATOR TMODH-TMODL TOV0 CH0MAX CH0F MS0A CHANNEL 1 16-BIT COMPARATOR TCH1H-TCH1L 16-BIT LATCH MS1A CHANNEL 2 16-BIT COMPARATOR TCH2H-TCH2L 16-BIT LATCH MS2A CHANNEL 3 16-BIT COMPARATOR TCH3H-TCH3L 16-BIT LATCH MS3A CHANNEL 4 16-BIT COMPARATOR TCH4H-TCH4L 16-BIT LATCH MS4A CHANNEL 5 16-BIT COMPARATOR TCH5H-TCH5L 16-BIT LATCH MS5A CH5IE CH5F ELS5B ELS5A MS4B CH4IE TOV5 CH5MAX CH4F ELS4B ELS4A CH3IE TOV4 CH5MAX CH3F ELS3B ELS3A MS2B CH2IE TOV3 CH3MAX CH2F ELS2B ELS2A CH1IE TOV2 CH2MAX CH1F ELS1B ELS1A CH0IE TOV1 CH1MAX
16-BIT COMPARATOR TCH0H-TCH0L 16-BIT LATCH MS0B
PTE2 LOGIC INTERRUPT LOGIC
PTE2/TCH0
PTE3 LOGIC INTERRUPT LOGIC
PTE3/TCH1
PTF0 LOGIC INTERRUPT LOGIC
PTF0/TCH2
PTF1 LOGIC INTERRUPT LOGIC
PTF1/TCH3
PTF2 LOGIC INTERRUPT LOGIC
PTF2/TCH4
PTF3 LOGIC INTERRUPT LOGIC
PTF3/TCH5
Figure 16-1. TIM Block Diagram
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM) Advance Information 207
NON-DISCLOSURE
AGREEMENT
CHANNEL 0
ELS0B
ELS0A
REQUIRED
Timer Interface (TIM) REQUIRED
Table 16-1. TIM I/O Register Summary
Addr. $0020 $0021 $0022 $0023 $0024 Register Name TIM Status/Control Register (TSC) Reserved TIM Counter Register High (TCNTH) TIM Counter Register Low (TCNTL) TIM Counter Modulo Reg. High (TMODH) TIM Counter Modulo Reg. Low (TMODL) TIM Ch. 0 Status/Control Register (TSC0) TIM Ch. 0 Register High (TCH0H) TIM Ch. 0 Register Low (TCH0L) TIM Ch. 1 Status/Control Register (TSC1) TIM Ch. 1 Register High (TCH1H) TIM Ch. 1 Register Low (TCH1L) TIM Ch. 2 Status/Control Register (TSC2) TIM Ch. 2 Register High (TCH2H) TIM Ch. 2 Register Low (TCH2L) TIM Ch. 3 Status/Control Register (TSC3) TIM Ch. 3 Register High (TCH3H) TIM Ch. 3 Register Low (TCH3L) TIM Ch. 4 Status/Control Register (TSC4) TIM Ch. 4 Register High (TCH4H) TIM Ch. 4 Register Low (TCH4L) TIM Ch. 5 Status/Control Register (TSC5) TIM Ch. 5 Register High (TCH5H) TIM Ch. 5 Register Low (TCH5L) Bit 7 TOF R Bit 15 Bit 7 Bit 15 Bit 7 CH0F Bit 15 Bit 7 CH1F Bit 15 Bit 7 CH2F Bit 15 Bit 7 CH3F Bit 15 Bit 7 CH4F Bit 15 Bit 7 CH5F Bit 15 Bit 7 6 TOIE R 14 6 14 6 CH0IE 14 6 CH1IE 14 6 CH2IE 14 6 CH3IE 14 6 CH4IE 14 6 CH5IE 14 6 5 TSTOP R 13 5 13 5 MS0B 13 5 0 13 5 MS2B 13 5 0 13 5 MS4B 13 5 0 13 5 4 TRST R 12 4 12 4 MS0A 12 4 MS1A 12 4 MS2A 12 4 MS3A 12 4 MS4A 12 4 MS5A 12 4 3 0 R 11 3 11 3 ELS0B 11 3 ELS1B 11 3 ELS2B 11 3 ELS3B 11 3 ELS4B 11 3 ELS5B 11 3 2 PS2 R 10 2 10 2 ELS0A 10 2 ELS1A 10 2 ELS2A 10 2 ELS3A 10 2 ELS4A 10 2 ELS5A 10 2 1 PS1 R 9 1 9 1 TOV0 9 1 TOV1 9 1 TOV2 9 1 TOV3 9 1 TOV4 9 1 TOV5 9 1 Bit 0 PS0 R Bit 8 Bit 0 Bit 8 Bit 0 CH0MAX Bit 8 Bit 0 CH1MAX Bit 8 Bit 0 CH2MAX Bit 8 Bit 0 CH3MAX Bit 8 Bit 0 CH4MAX Bit 8 Bit 0 CH5MAX Bit 8 Bit 0
AGREEMENT NON-DISCLOSURE
$0025 $0026 $0027 $0028 $0029 $002A $002B $002C $002D $002E $002F $0030 $0031 $0032 $0033 $0034 $0035 $0036 $0037
R
= Reserved
Advance Information 208 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) Functional Description
16.4 Functional Description
Figure 16-1 shows the TIM structure. The central component of the TIM is the 16-bit TIM counter that can operate as a free-running counter or a modulo up-counter. The TIM counter provides the timing reference for the input capture and output compare functions. The TIM counter modulo registers, TMODH-TMODL, control the modulo value of the TIM counter. Software can read the TIM counter value at any time without affecting the counting sequence. The six TIM channels are programmable independently as input capture or output compare channels.
16.4.1 TIM Counter Prescaler The TIM clock source can be one of the seven prescaler outputs or the TIM clock pin, PTD6/ATD14/TCLK. The prescaler generates seven clock rates from the internal bus clock. The prescaler select bits, PS[2-0], in the TIM status and control register select the TIM clock source.
An input capture function has three basic parts: edge select logic, an input capture latch, and a 16-bit counter. Two 8-bit registers, which make up the 16-bit input capture register, are used to latch the value of the free-running counter after the corresponding input capture edge detector senses a defined transition. The polarity of the active edge is programmable. The level transition which triggers the counter transfer is defined by the corresponding input edge bits (ELSxB and ELSxA in TSC0 through TSC5 control registers with x referring to the active channel number). When an active edge occurs on the pin of an input capture channel, the TIM latches the contents of the TIM counter into the TIM channel registers, TCHxH-TCHxL. Input captures can generate TIM CPU interrupt requests. Software can determine that an input capture event has occurred by enabling input capture interrupts or by polling the status flag bit.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 209
NON-DISCLOSURE
16.4.2 Input Capture
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
The result obtained by an input capture will be one more than the value of the free-running counter on the rising edge of the internal bus clock preceding the external transition. This delay is required for internal synchronization. The free-running counter contents are transferred to the TIM channel registers (TCHxH-TCHxL) (see 16.9.5 TIM Channel Registers) on each proper signal transition regardless of whether the TIM channel flag (CH0F-CH5F in TSC0-TSC5 registers) is set or clear. When the status flag is set, a CPU interrupt is generated if enabled. The value of the count latched or "captured" is the time of the event. Because this value is stored in the input capture register when the actual event occurs, user software can respond to this event at a later time and determine the actual time of the event. However, this must be done prior to another input capture on the same pin; otherwise, the previous time value will be lost. By recording the times for successive edges on an incoming signal, software can determine the period and/or pulse width of the signal. To measure a period, two successive edges of the same polarity are captured. To measure a pulse width, two alternate polarity edges are captured. Software should track the overflows at the 16-bit module counter to extend its range. Another use for the input capture function is to establish a time reference. In this case, an input capture function is used in conjunction with an output compare function. For example, to activate an output signal a specified number of clock cycles after detecting an input event (edge), use the input capture function to record the time at which the edge occurred. A number corresponding to the desired delay is added to this captured value and stored to an output compare register (see 16.9.5 TIM Channel Registers). Because both input captures and output compares are referenced to the same 16-bit modulo counter, the delay can be controlled to the resolution of the counter independent of software latencies. Reset does not affect the contents of the input capture channel (TCHxH-TCHxL) registers.
NON-DISCLOSURE
Advance Information 210
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Timer Interface (TIM) MOTOROLA
Timer Interface (TIM) Functional Description
16.4.3 Output Compare With the output compare function, the TIM can generate a periodic pulse with a programmable polarity, duration, and frequency. When the counter reaches the value in the registers of an output compare channel, the TIM can set, clear, or toggle the channel pin. Output compares can generate TIM CPU interrupt requests. 16.4.3.1 Unbuffered Output Compare Any output compare channel can generate unbuffered output compare pulses as described in 16.4.3 Output Compare. The pulses are unbuffered because changing the output compare value requires writing the new value over the old value currently in the TIM channel registers. An unsynchronized write to the TIM channel registers to change an output compare value could cause incorrect operation for up to two counter overflow periods. For example, writing a new value before the counter reaches the old value but after the counter reaches the new value prevents any compare during that counter overflow period. Also, using a TIM overflow interrupt routine to write a new, smaller output compare value may cause the compare to be missed. The TIM may pass the new value before it is written. Use the following methods to synchronize unbuffered changes in the output compare value on channel x: * When changing to a smaller value, enable channel x output compare interrupts and write the new value in the output compare interrupt routine. The output compare interrupt occurs at the end of the current output compare pulse. The interrupt routine has until the end of the counter overflow period to write the new value. When changing to a larger output compare value, enable channel x TIM overflow interrupts and write the new value in the TIM overflow interrupt routine. The TIM overflow interrupt occurs at the end of the current counter overflow period. Writing a larger value in an output compare interrupt routine (at the end of the current pulse) could cause two output compares to occur in the same counter overflow period.
*
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 211
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
16.4.3.2 Buffered Output Compare Channels 0 and 1 can be linked to form a buffered output compare channel whose output appears on the PTE2/TCH0 pin. The TIM channel registers of the linked pair alternately control the output. Setting the MS0B bit in TIM channel 0 status and control register (TSC0) links channel 0 and channel 1. The output compare value in the TIM channel 0 registers initially controls the output on the PTE2/TCH0 pin. Writing to the TIM channel 1 registers enables the TIM channel 1 registers to synchronously control the output after the TIM overflows. At each subsequent overflow, the TIM channel registers (0 or 1) that control the output are the ones written to last. TSC0 controls and monitors the buffered output compare function, and TIM channel 1 status and control register (TSC1) is unused. While the MS0B bit is set, the channel 1 pin, PTE3/TCH1, is available as a general-purpose I/O pin. Channels 2 and 3 can be linked to form a buffered output compare channel whose output appears on the PTF0/TCH2 pin. The TIM channel registers of the linked pair alternately control the output. Setting the MS2B bit in TIM channel 2 status and control register (TSC2) links channel 2 and channel 3. The output compare value in the TIM channel 2 registers initially controls the output on the PTF0/TCH2 pin. Writing to the TIM channel 3 registers enables the TIM channel 3 registers to synchronously control the output after the TIM overflows. At each subsequent overflow, the TIM channel registers (2 or 3) that control the output are the ones written to last. TSC2 controls and monitors the buffered output compare function, and TIM channel 3 status and control register (TSC3) is unused. While the MS2B bit is set, the channel 3 pin, PTF1/TCH3, is available as a general-purpose I/O pin. Channels 4 and 5 can be linked to form a buffered output compare channel whose output appears on the PTF2/TCH4 pin. The TIM channel registers of the linked pair alternately control the output. Setting the MS4B bit in TIM channel 4 status and control register (TSC4) links channel 4 and channel 5. The output compare value in the TIM channel 4 registers initially controls the output on the PTF2/TCH4 pin. Writing to the TIM channel 5 registers enables the TIM channel 5
NON-DISCLOSURE
Advance Information 212
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Timer Interface (TIM) MOTOROLA
Timer Interface (TIM) Functional Description
registers to synchronously control the output after the TIM overflows. At each subsequent overflow, the TIM channel registers (4 or 5) that control the output are the ones written to last. TSC4 controls and monitors the buffered output compare function, and TIM channel 5 status and control register (TSC5) is unused. While the MS4B bit is set, the channel 5 pin, PTF3/TCH5, is available as a general-purpose I/O pin.
NOTE:
16.4.4 Pulse Width Modulation (PWM) By using the toggle-on-overflow feature with an output compare channel, the TIM can generate a PWM signal. The value in the TIM counter modulo registers determines the period of the PWM signal. The channel pin toggles when the counter reaches the value in the TIM counter modulo registers. The time between overflows is the period of the PWM signal. As Figure 16-2 shows, the output compare value in the TIM channel registers determines the pulse width of the PWM signal. The time between overflow and output compare is the pulse width. Program the TIM to clear the channel pin on output compare if the state of the PWM pulse is logic 1. Program the TIM to set the pin if the state of the PWM pulse is logic 0.
OVERFLOW PERIOD OVERFLOW OVERFLOW
PULSE WIDTH PTEx/TCHx
OUTPUT COMPARE
OUTPUT COMPARE
OUTPUT COMPARE
Figure 16-2. PWM Period and Pulse Width
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM) Advance Information 213
NON-DISCLOSURE
AGREEMENT
In buffered output compare operation, do not write new output compare values to the currently active channel registers. Writing to the active channel registers is the same as generating unbuffered output compares.
REQUIRED
Timer Interface (TIM) REQUIRED
The value in the TIM counter modulo registers and the selected prescaler output determines the frequency of the PWM output. The frequency of an 8-bit PWM signal is variable in 256 increments. Writing $00FF (255) to the TIM counter modulo registers produces a PWM period of 256 times the internal bus clock period if the prescaler select value is $000 (see 16.9.1 TIM Status and Control Register). The value in the TIM channel registers determines the pulse width of the PWM output. The pulse width of an 8-bit PWM signal is variable in 256 increments. Writing $0080 (128) to the TIM channel registers produces a duty cycle of 128/256 or 50%. 16.4.4.1 Unbuffered PWM Signal Generation Any output compare channel can generate unbuffered PWM pulses as described in 16.4.4 Pulse Width Modulation (PWM). The pulses are unbuffered because changing the pulse width requires writing the new pulse width value over the value currently in the TIM channel registers. An unsynchronized write to the TIM channel registers to change a pulse width value could cause incorrect operation for up to two PWM periods. For example, writing a new value before the counter reaches the old value but after the counter reaches the new value prevents any compare during that PWM period. Also, using a TIM overflow interrupt routine to write a new, smaller pulse width value may cause the compare to be missed. The TIM may pass the new value before it is written to the timer channel (TCHxH/TCHxL) registers. Use the following methods to synchronize unbuffered changes in the PWM pulse width on channel x: * When changing to a shorter pulse width, enable channel x output compare interrupts and write the new value in the output compare interrupt routine. The output compare interrupt occurs at the end of the current pulse. The interrupt routine has until the end of the PWM period to write the new value. When changing to a longer pulse width, enable channel x TIM overflow interrupts and write the new value in the TIM overflow interrupt routine. The TIM overflow interrupt occurs at the end of
NON-DISCLOSURE
AGREEMENT
*
Advance Information 214 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) Functional Description
the current PWM period. Writing a larger value in an output compare interrupt routine (at the end of the current pulse) could cause two output compares to occur in the same PWM period.
NOTE:
In PWM signal generation, do not program the PWM channel to toggle on output compare. Toggling on output compare prevents reliable 0% duty cycle generation and removes the ability of the channel to self-correct in the event of software error or noise. Toggling on output compare also can cause incorrect PWM signal generation when changing the PWM pulse width to a new, much larger value.
16.4.4.2 Buffered PWM Signal Generation Channels 0 and 1 can be linked to form a buffered PWM channel whose output appears on the PTE2/TCH0 pin. The TIM channel registers of the linked pair alternately control the pulse width of the output. Setting the MS0B bit in TIM channel 0 status and control register (TSC0) links channel 0 and channel 1. The TIM channel 0 registers initially control the pulse width on the PTE2/TCH0 pin. Writing to the TIM channel 1 registers enables the TIM channel 1 registers to synchronously control the pulse width at the beginning of the next PWM period. At each subsequent overflow, the TIM channel registers (0 or 1) that control the pulse width are the ones written to last. TSC0 controls and monitors the buffered PWM function, and TIM channel 1 status and control register (TSC1) is unused. While the MS0B bit is set, the channel 1 pin, PTE3/TCH1, is available as a general-purpose I/O pin. Channels 2 and 3 can be linked to form a buffered PWM channel whose output appears on the PTF0/TCH2 pin. The TIM channel registers of the linked pair alternately control the pulse width of the output. Setting the MS2B bit in TIM channel 2 status and control register (TSC2) links channel 2 and channel 3. The TIM channel 2 registers initially control the pulse width on the PTF0/TCH2 pin. Writing to the TIM channel 3 registers enables the TIM channel 3 registers to synchronously control the pulse width at the beginning of the next PWM period. At each subsequent overflow, the TIM channel registers (2 or 3) that control the pulse width are the ones written to last. TSC2 controls and monitors the buffered PWM function, and TIM channel 3 status and
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM) Advance Information 215
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
control register (TSC3) is unused. While the MS2B bit is set, the channel 3 pin, PTF1/TCH3, is available as a general-purpose I/O pin. Channels 4 and 5 can be linked to form a buffered PWM channel whose output appears on the PTF2/TCH4 pin. The TIM channel registers of the linked pair alternately control the pulse width of the output. Setting the MS4B bit in TIM channel 4 status and control register (TSC4) links channel 4 and channel 5. The TIM channel 4 registers initially control the pulse width on the PTF2/TCH4 pin. Writing to the TIM channel 5 registers enables the TIM channel 5 registers to synchronously control the pulse width at the beginning of the next PWM period. At each subsequent overflow, the TIM channel registers (4 or 5) that control the pulse width are the ones written to last. TSC4 controls and monitors the buffered PWM function, and TIM channel 5 status and control register (TSC5) is unused. While the MS4B bit is set, the channel 5 pin, PTF3/TCH5, is available as a general-purpose I/O pin.
AGREEMENT
NOTE:
In buffered PWM signal generation, do not write new pulse width values to the currently active channel registers. Writing to the active channel registers is the same as generating unbuffered PWM signals.
NON-DISCLOSURE
16.4.4.3 PWM Initialization To ensure correct operation when generating unbuffered or buffered PWM signals, use the following initialization procedure: 1. In the TIM status and control register (TSC): a. Stop the TIM counter by setting the TIM stop bit, TSTOP. b. Reset the TIM counter by setting the TIM reset bit, TRST. 2. In the TIM counter modulo registers (TMODH-TMODL), write the value for the required PWM period. 3. In the TIM channel x registers (TCHxH-TCHxL), write the value for the required pulse width.
Advance Information 216 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) Functional Description
4. In TIM channel x status and control register (TSCx): a. Write 0-1 (for unbuffered output compare or PWM signals) or 1-0 (for buffered output compare or PWM signals) to the mode select bits, MSxB-MSxA. (See Table 16-3.) b. Write 1 to the toggle-on-overflow bit, TOVx. c. Write 1-0 (to clear output on compare) or 1-1 (to set output on compare) to the edge/level select bits, ELSxB-ELSxA. The output action on compare must force the output to the complement of the pulse width level. (See Table 16-3.)
NOTE:
In PWM signal generation, do not program the PWM channel to toggle on output compare. Toggling on output compare prevents reliable 0% duty cycle generation and removes the ability of the channel to self-correct in the event of software error or noise. Toggling on output compare can also cause incorrect PWM signal generation when changing the PWM pulse width to a new, much larger value.
5. In the TIM status control register (TSC), clear the TIM stop bit, TSTOP. Setting MS0B links channels 0 and 1 and configures them for buffered PWM operation. The TIM channel 0 registers (TCH0H-TCH0L) initially control the buffered PWM output. TIM status control register 0 (TSC0) controls and monitors the PWM signal from the linked channels. MS0B takes priority over MS0A. Setting MS2B links channels 2 and 3 and configures them for buffered PWM operation. The TIM channel 2 registers (TCH2H-TCH2L) initially control the PWM output. TIM status control register 2 (TSC2) controls and monitors the PWM signal from the linked channels. MS2B takes priority over MS2A. Setting MS4B links channels 4 and 5 and configures them for buffered PWM operation. The TIM channel 4 registers (TCH4H-TCH4L) initially control the PWM output. TIM status control register 4 (TSC4) controls and monitors the PWM signal from the linked channels. MS4B takes priority over MS4A.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 217
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
Clearing the toggle-on-overflow bit, TOVx, inhibits output toggles on TIM overflows. Subsequent output compares try to force the output to a state it is already in and have no effect. The result is a 0% duty cycle output. Setting the channel x maximum duty cycle bit (CHxMAX) and clearing the TOVx bit generates a 100% duty cycle output. (See 16.9.4 TIM Channel Status and Control Registers.)
AGREEMENT
16.5 Interrupts
The following TIM sources can generate interrupt requests: * TIM overflow flag (TOF) -- The TOF bit is set when the TIM counter value rolls over to $0000 after matching the value in the TIM counter modulo registers. The TIM overflow interrupt enable bit, TOIE, enables TIM overflow CPU interrupt requests. TOF and TOIE are in the TIM status and control register. TIM channel flags (CH5F-CH0F) -- The CHxF bit is set when an input capture or output compare occurs on channel x. Channel x TIM CPU interrupt requests are controlled by the channel x interrupt enable bit, CHxIE.
*
NON-DISCLOSURE
16.6 Low-Power Modes
The WAIT and STOP instructions put the MCU in low-power standby modes.
16.6.1 Wait Mode The TIM remains active after the execution of a WAIT instruction. In wait mode, the TIM registers are not accessible by the CPU. Any enabled CPU interrupt request from the TIM can bring the MCU out of wait mode. If TIM functions are not required during wait mode, reduce power consumption by stopping the TIM before executing the WAIT instruction.
Advance Information 218 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) TIM During Break Interrupts
16.6.2 Stop Mode The TIM is inactive after the execution of a STOP instruction. The STOP instruction does not affect register conditions or the state of the TIM counter. TIM operation resumes when the MCU exits stop mode.
16.7 TIM During Break Interrupts
A break interrupt stops the TIM counter. The system integration module (SIM) controls whether status bits in other modules can be cleared during the break state. The BCFE bit in the SIM break flag control register (SBFCR) enables software to clear status bits during the break state. (See 9.8.3 SIM Break Flag Control Register.) To allow software to clear status bits during a break interrupt, write a logic 1 to the BCFE bit. If a status bit is cleared during the break state, it remains cleared when the MCU exits the break state. To protect status bits during the break state, write a logic 0 to the BCFE bit. With BCFE at logic 0 (its default state), software can read and write I/O registers during the break state without affecting status bits. Some status bits have a 2-step read/write clearing procedure. If software does the first step on such a bit before the break, the bit cannot change during the break state as long as BCFE is at logic 0. After the break, doing the second step clears the status bit.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 219
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED 16.8 I/O Signals
Port D shares one of its pins with the TIM. Port E shares two of its pins with the TIM and port F shares four of its pins with the TIM. PTD6/ATD14/TCLK is an external clock input to the TIM prescaler. The six TIM channel I/O pins are PTE2/TCH0, PTE3/TCH1, PTF0/TCH2, PTF1/TCH3, PTF2/TCH4, and PTF3/TCH5.
16.8.1 TIM Clock Pin (PTD6/ATD14/TCLK)
AGREEMENT
PTD6/ATD14/TCLK is an external clock input that can be the clock source for the TIM counter instead of the prescaled internal bus clock. Select the PTD6/ATD14/TCLK input by writing logic 1s to the three prescaler select bits, PS[2-0]. (See 16.9.1 TIM Status and Control Register.) The minimum TCLK pulse width, TCLKLMIN or TCLKHMIN, is: 1 ------------------------------------ + tSU bus frequency The maximum TCLK frequency is the least: 4 MHz or bus frequency / 2. PTD6/ATD14/TCLK is available as a general-purpose I/O pin or ADC channel when not used as the TIM clock input. When the PTD6/ATD14/TCLK pin is the TIM clock input, it is an input regardless of the state of the DDRD6 bit in data direction register D.
NON-DISCLOSURE
16.8.2 TIM Channel I/O Pins (PTF3/TCH5-PTF0/TCH2 and PTE3/TCH1-PTE2/TCH0) Each channel I/O pin is programmable independently as an input capture pin or an output compare pin. PTE2/TCH0, PTE6/TCH2, and PTF2/TCH4 can be configured as buffered output compare or buffered PWM pins.
Advance Information 220 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) I/O Registers
16.9 I/O Registers
These I/O registers control and monitor TIM operation: * * * * * TIM status and control register (TSC) TIM control registers (TCNTH-TCNTL) TIM counter modulo registers (TMODH-TMODL) TIM channel status and control registers (TSC0, TSC1, TSC2, TSC3, TSC4, and TSC5) TIM channel registers (TCH0H-TCH0L, TCH1H-TCH1L, TCH2H-TCH2L, TCH3H-TCH3L, TCH4H-TCH4L, and TCH5H-TCH5L)
16.9.1 TIM Status and Control Register The TIM status and control register: * * * * * Enables TIM overflow interrupts Flags TIM overflows Stops the TIM counter
Prescales the TIM counter clock
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 221
NON-DISCLOSURE
Resets the TIM counter
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
Address:
$0020 Bit 7 6 TOIE 0 = Reserved 5 TSTOP 1 4 0 TRST 0 3 0 R 0 2 PS2 0 1 PS1 0 Bit 0 PS0 0
Read: Write: Reset:
TOF 0 0 R
Figure 16-3. TIM Status and Control Register (TSC) TOF -- TIM Overflow Flag Bit This read/write flag is set when the TIM counter resets to $0000 after reaching the modulo value programmed in the TIM counter modulo registers. Clear TOF by reading the TIM status and control register when TOF is set and then writing a logic 0 to TOF. If another TIM overflow occurs before the clearing sequence is complete, then writing logic 0 to TOF has no effect. Therefore, a TOF interrupt request cannot be lost due to inadvertent clearing of TOF. Reset clears the TOF bit. Writing a logic 1 to TOF has no effect. 1 = TIM counter has reached modulo value 0 = TIM counter has not reached modulo value TOIE -- TIM Overflow Interrupt Enable Bit This read/write bit enables TIM overflow interrupts when the TOF bit becomes set. Reset clears the TOIE bit. 1 = TIM overflow interrupts enabled 0 = TIM overflow interrupts disabled TSTOP -- TIM Stop Bit This read/write bit stops the TIM counter. Counting resumes when TSTOP is cleared. Reset sets the TSTOP bit, stopping the TIM counter until software clears the TSTOP bit. 1 = TIM counter stopped 0 = TIM counter active
NON-DISCLOSURE
AGREEMENT
NOTE:
Do not set the TSTOP bit before entering wait mode if the TIM is required to exit wait mode. Also when the TSTOP bit is set and the timer is configured for input capture operation, input captures are inhibited until the TSTOP bit is cleared.
MC68HC08AS32 -- Rev. 3.0 Timer Interface (TIM) MOTOROLA
Advance Information 222
Timer Interface (TIM) I/O Registers
TRST -- TIM Reset Bit Setting this write-only bit resets the TIM counter and the TIM prescaler. Setting TRST has no effect on any other registers. Counting resumes from $0000. TRST is cleared automatically after the TIM counter is reset and always reads as logic 0. Reset clears the TRST bit. 1 = Prescaler and TIM counter cleared 0 = No effect
NOTE:
PS[2-0] -- Prescaler Select Bits These read/write bits select either the PTD6/ATD14/TCLK pin or one of the seven prescaler outputs as the input to the TIM counter as Table 16-2 shows. Reset clears the PS[2-0] bits. Table 16-2. Prescaler Selection
PS[2-0] 000 001 010 011 100 101 110 111 TIM Clock Source Internal Bus Clock /1 Internal Bus Clock / 2 Internal Bus Clock / 4 Internal Bus Clock / 8 Internal Bus Clock / 16 Internal Bus Clock / 32 Internal Bus Clock / 64 PTD6/ATD14/TCLK
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 223
NON-DISCLOSURE
AGREEMENT
Setting the TSTOP and TRST bits simultaneously stops the TIM counter at a value of $0000.
REQUIRED
Timer Interface (TIM) REQUIRED
16.9.2 TIM Counter Registers The two read-only TIM counter registers contain the high and low bytes of the value in the TIM counter. Reading the high byte (TCNTH) latches the contents of the low byte (TCNTL) into a buffer. Subsequent reads of TCNTH do not affect the latched TCNTL value until TCNTL is read. Reset clears the TIM counter registers. Setting the TIM reset bit (TRST) also clears the TIM counter registers.
NOTE:
AGREEMENT
If TCNTH is read during a break interrupt, be sure to unlatch TCNTL by reading TCNTL before exiting the break interrupt. Otherwise, TCNTL retains the value latched during the break.
Register Name and Address TCNTH -- $0022 Bit 7 Read: Write: Reset: BIT 15 R 0 6 BIT 14 R 0 5 BIT 13 R 0 4 BIT 12 R 0 3 BIT 11 R 0 2 BIT 10 R 0 1 BIT 9 R 0 Bit 0 BIT 8 R 0
Register Name and Address TCNTL -- $0023
NON-DISCLOSURE
Bit 7 Read: Write: Reset: BIT 7 R 0 R
6 BIT 6 R 0 R = Reserved
5 BIT 5 R 0
4 BIT 4 R 0
3 BIT 3 R 0
2 BIT 2 R 0
1 BIT 1 R 0
Bit 0 BIT 0 R 0
Figure 16-4. TIM Counter Registers (TCNTH and TCNTL)
Advance Information 224 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) I/O Registers
16.9.3 TIM Counter Modulo Registers The read/write TIM modulo registers contain the modulo value for the TIM counter. When the TIM counter reaches the modulo value, the overflow flag (TOF) becomes set, and the TIM counter resumes counting from $0000 at the next clock. Writing to the high byte (TMODH) inhibits the TOF bit and overflow interrupts until the low byte (TMODL) is written. Reset sets the TIM counter modulo registers.
Register Name and Address TMODH -- $0024
Read: BIT 15 Write: Reset: 1 1 1 1 1 1 1 1 BIT 14 BIT 13 BIT 12 BIT 11 BIT 10 BIT 9 BIT 8
Register Name and Address TMODL -- $0025 Bit 7 Read: BIT 7 Write: Reset: 1 1 1 1 1 1 1 1 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0 6 5 4 3 2 1 Bit 0
Figure 16-5. TIM Counter Modulo Registers (TMODH and TMODL)
NOTE:
Reset the TIM counter before writing to the TIM counter modulo registers.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 225
NON-DISCLOSURE
AGREEMENT
Bit 7
6
5
4
3
2
1
Bit 0
REQUIRED
Timer Interface (TIM) REQUIRED
16.9.4 TIM Channel Status and Control Registers Each of the TIM channel status and control registers: * * * * * * * * Flags input captures and output compares Enables input capture and output compare interrupts Selects input capture, output compare, or PWM operation Selects high, low, or toggling output on output compare Selects rising edge, falling edge, or any edge as the active input capture trigger Selects output toggling on TIM overflow Selects 100% PWM duty cycle Selects buffered or unbuffered output compare/PWM operation
AGREEMENT
Register Name and Address TSC0 -- $0026 Bit 7 Read: Write: CH0F CH0IE 0 0 0 0 0 0 0 0 0 Reset: MS0B MS0A ELS0B ELS0A TOV0 CH0MAX 6 5 4 3 2 1 Bit 0
NON-DISCLOSURE
Register Name and Address TSC1 -- $0029 Bit 7 Read: Write: Reset: CH1F CH1IE 0 0 R 0 = Reserved R 0 0 0 0 0 0 6 5 0 MS1A ELS1B ELS1A TOV1 CH1MAX 4 3 2 1 Bit 0
Figure 16-6. TIM Channel Status and Control Registers (TSC0-TSC5)
Advance Information 226 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) I/O Registers
Register Name and Address TSC2 -- $002C Bit 7 Read: Write: Reset: CH2F CH2IE 0 0 0 0 0 0 0 0 0 MS2B MS2A ELS2B ELS2A TOV2 CH2MAX 6 5 4 3 2 1 Bit 0
Register Name and Address TSC3 -- $002F Bit 7 Read: Write: Reset: CH3F CH3IE 0 0 0 R 0 0 0 0 0 0 6 5 0 MS3A ELS3B ELS3A TOV3 CH3MAX 4 3 2 1 Bit 0
Register Name and Address TSC4 -- $0032 Bit 7 Read: Write: Reset: CH4F CH4IE 0 0 0 0 0 0 0 0 0 MS4B MS4A ELS4B ELS4A TOV4 CH4MAX 6 5 4 3 2 1 Bit 0
Register Name and Address TSC5 -- $0035 Bit 7 Read: Write: Reset: CH5F CH5IE 0 0 R 0 R = Reserved R 0 0 0 0 0 0 6 5 0 MS5A ELS5B ELS5A TOV5 CH5MAX 4 3 2 1 Bit 0
Figure 16-6. TIM Channel Status and Control Registers (TSC0-TSC5) (Continued)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 227
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
CHxF -- Channel x Flag Bit When channel x is an input capture channel, this read/write bit is set when an active edge occurs on the channel x pin. When channel x is an output compare channel, CHxF is set when the value in the TIM counter registers matches the value in the TIM channel x registers. When CHxIE = 0, clear CHxF by reading TIM channel x status and control register with CHxF set, and then writing a logic 0 to CHxF. If another interrupt request occurs before the clearing sequence is complete, then writing logic 0 to CHxF has no effect. Therefore, an interrupt request cannot be lost due to inadvertent clearing of CHxF. Reset clears the CHxF bit. Writing a logic 1 to CHxF has no effect. 1 = Input capture or output compare on channel x 0 = No input capture or output compare on channel x CHxIE -- Channel x Interrupt Enable Bit This read/write bit enables TIM CPU interrupts on channel x. Reset clears the CHxIE bit. 1 = Channel x CPU interrupt requests enabled 0 = Channel x CPU interrupt requests disabled MSxB -- Mode Select Bit B
NON-DISCLOSURE
AGREEMENT
This read/write bit selects buffered output compare/PWM operation. MSxB exists only in the TIM channel 0, TIM channel 2, and TIM channel 4 status and control registers. Setting MS0B disables the channel 1 status and control register and reverts TCH1 pin to general-purpose I/O. Setting MS2B disables the channel 3 status and control register and reverts TCH3 pin to general-purpose I/O. Setting MS4B disables the channel 5 status and control register and reverts TCH5 pin to general-purpose I/O. Reset clears the MSxB bit. 1 = Buffered output compare/PWM operation enabled 0 = Buffered output compare/PWM operation disabled
Advance Information 228 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) I/O Registers
MSxA -- Mode Select Bit A When ELSxB-ELSxA 00, this read/write bit selects either input capture operation or unbuffered output compare/PWM operation. (See Table 16-3.) 1 = Unbuffered output compare/PWM operation 0 = Input capture operation When ELSxB-ELSxA = 00, this read/write bit selects the initial output level of the TCHx pin once PWM, input capture, or output compare operation is enabled. (See Table 16-3.) Reset clears the MSxA bit. 1 = Initial output level low 0 = Initial output level high
NOTE:
Before changing a channel function by writing to the MSxB or MSxA bit, set the TSTOP and TRST bits in the TIM status and control register (TSC).
ELSxB and ELSxA -- Edge/Level Select Bits When channel x is an input capture channel, these read/write bits control the active edge-sensing logic on channel x. When channel x is an output compare channel, ELSxB and ELSxA control the channel x output behavior when an output compare occurs. When ELSxB and ELSxA are both clear, channel x is not connected to port E or port F, and pin PTEx/TCHx or pin PTFx/TCHx is available as a general-purpose I/O pin. However, channel x is at a state determined by these bits and becomes transparent to the respective pin when PWM, input capture, or output compare mode is ena bled. Table 16-3 shows how ELSxB and ELSxA work. Reset clears the ELSxB and ELSxA bits.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 229
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
Table 16-3. Mode, Edge, and Level Selection
MSxB-MSxA X0 ELSxB-ELSxA 00 Output Preset X1 00 00 01 10 11 01 10 11 01 10 11 Output Compare or PWM Buffered Output Compare orBuffered PWM Input Capture Mode Configuration Pin under Port Control; Initialize Timer Output Level High Pin under Port Control; Initialize Timer Output Level Low Capture on Rising Edge Only Capture on Falling Edge Only Capture on Rising or Falling Edge Toggle Output on Compare Clear Output on Compare Set Output on Compare Toggle Output on Compare Clear Output on Compare Set Output on Compare
AGREEMENT
00 00 01 01 01 1X 1X 1X
NON-DISCLOSURE
NOTE:
Before enabling a TIM channel register for input capture operation, make sure that the PTEx/TCHx pin or PTFx/TCHx pin is stable for at least two bus clocks.
TOVx -- Toggle-On-Overflow Bit When channel x is an output compare channel, this read/write bit controls the behavior of the channel x output when the TIM counter overflows. When channel x is an input capture channel, TOVx has no effect. Reset clears the TOVx bit. 1 = Channel x pin toggles on TIM counter overflow. 0 = Channel x pin does not toggle on TIM counter overflow.
NOTE:
When TOVx is set, a TIM counter overflow takes precedence over a channel x output compare if both occur at the same time.
Advance Information 230 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) I/O Registers
CHxMAX -- Channel x Maximum Duty Cycle Bit When the TOVx bit is at logic 0, setting the CHxMAX bit forces the duty cycle of buffered and unbuffered PWM signals to 100%. As Figure 16-7 shows, the CHxMAX bit takes effect in the cycle after it is set or cleared. The output stays at the 100% duty cycle level until the cycle after CHxMAX is cleared.
OVERFLOW OVERFLOW OVERFLOW OVERFLOW OVERFLOW
PTEx/TCHx
OUTPUT COMPARE CHxMAX
OUTPUT COMPARE
OUTPUT COMPARE
OUTPUT COMPARE
Figure 16-7. CHxMAX Latency
16.9.5 TIM Channel Registers These read/write registers contain the captured TIM counter value of the input capture function or the output compare value of the output compare function. The state of the TIM channel registers after reset is unknown. In input capture mode (MSxB-MSxA = 0-0), reading the high byte of the TIM channel x registers (TCHxH) inhibits input captures until the low byte (TCHxL) is read. In output compare mode (MSxB-MSxA 0-0), writing to the high byte of the TIM channel x registers (TCHxH) inhibits output compares until the low byte (TCHxL) is written.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 231
NON-DISCLOSURE
AGREEMENT
PERIOD
REQUIRED
Timer Interface (TIM) REQUIRED
Register Name and Address TCH0H -- $0027 Bit 7 Read: Bit 15 Write: Reset: Indeterminate after Reset Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 6 5 4 3 2 1 Bit 0
Register Name and Address TCH0L -- $0028
AGREEMENT
Bit 7 Read: Bit 7 Write: Reset:
6 Bit 6
5 Bit 5
4 Bit 4
3 Bit 3
2 Bit 2
1 Bit 1
Bit 0 Bit 0
Indeterminate after Reset
Register Name and Address TCH1H -- $002A Bit 7 Read: Bit 15 Write: Reset: Indeterminate after Reset Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 6 5 4 3 2 1 Bit 0
NON-DISCLOSURE
Register Name and Address TCH1L -- $002B Bit 7 Read: Bit 7 Write: Reset: Indeterminate after Reset Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 6 5 4 3 2 1 Bit 0
Register Name and Address TCH2H -- $002D Bit 7 Read: Bit 15 Write: Reset: Indeterminate after Reset Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 6 5 4 3 2 1 Bit 0
Figure 16-8. TIM Channel Registers (TCH0H/L-TCH3H/L) (Sheet 1 of 3)
Advance Information 232 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Timer Interface (TIM) I/O Registers
Register Name and Address TCH2L -- $002E Bit 7 Read: Bit 7 Write: Reset: Indeterminate after Reset Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 6 5 4 3 2 1 Bit 0
Register Name and Address TCH3H -- $0030 Bit 7 Read: Bit 15 Write: Reset: Indeterminate after Reset Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 6 5 4 3 2 1 Bit 0
Register Name and Address TCH3L -- $0031 Bit 7 Read: Bit 7 Write: Reset: Indeterminate after Reset Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 6 5 4 3 2 1 Bit 0
Register Name and Address TCH4H -- $0033 Bit 7 Read: Bit 15 Write: Reset: Indeterminate after Reset Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 6 5 4 3 2 1 Bit 0
Register Name and Address TCH4L -- $0034 Bit 7 Read: Bit 7 Write: Reset: Indeterminate after Reset Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 6 5 4 3 2 1 Bit 0
Figure 16-8. TIM Channel Registers (TCH0H/L-TCH3H/L) (Sheet 2 of 3)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Timer Interface (TIM)
Advance Information 233
NON-DISCLOSURE
AGREEMENT
REQUIRED
Timer Interface (TIM) REQUIRED
Register Name and Address TCH5H -- $0036 Bit 7 Read: Bit 15 Write: Reset: Indeterminate after Reset Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 6 5 4 3 2 1 Bit 0
Register Name and Address TCH5L -- $0037
AGREEMENT
Bit 7 Read: Bit 7 Write: Reset:
6 Bit 6
5 Bit 5
4 Bit 4
3 Bit 3
2 Bit 2
1 Bit 1
Bit 0 Bit 0
Indeterminate after Reset
Figure 16-8. TIM Channel Registers (TCH0H/L-TCH3H/L) (Sheet 3 of 3)
NON-DISCLOSURE
Advance Information 234 Timer Interface (TIM)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 17. Serial Communications Interface (SCI)
17.1 Contents
17.2 17.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
17.5 Receiver Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253 17.5.1 Error Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254 17.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 17.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 17.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255 17.7 SCI During Break Module Interrupts. . . . . . . . . . . . . . . . . . . .255
17.8 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256 17.8.1 PTE0/TxD (Transmit Data) . . . . . . . . . . . . . . . . . . . . . . . .256 17.8.2 PTE1/RxD (Receive Data) . . . . . . . . . . . . . . . . . . . . . . . .256
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 235
NON-DISCLOSURE
17.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 17.4.1 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 17.4.2 Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 17.4.3 Character Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240 17.4.4 Character Transmission . . . . . . . . . . . . . . . . . . . . . . . . . .241 17.4.5 Break Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 17.4.6 Idle Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 17.4.7 Inversion of Transmitted Output . . . . . . . . . . . . . . . . . . . .245 17.4.8 Transmitter Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 17.4.9 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246 17.4.10 Character Length. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 17.4.11 Character Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 17.4.12 Data Sampling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 17.4.13 Framing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 17.4.14 Receiver Wakeup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
17.9 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257 17.9.1 SCI Control Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .257 17.9.2 SCI Control Register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . .261 17.9.3 SCI Control Register 3 . . . . . . . . . . . . . . . . . . . . . . . . . . .263 17.9.4 SCI Status Register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .265 17.9.5 SCI Status Register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 17.9.6 SCI Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270 17.9.7 SCI Baud Rate Register . . . . . . . . . . . . . . . . . . . . . . . . . .271
AGREEMENT
17.2 Introduction
This section describes the serial communications interface module (SCI, Version D), which allows high-speed asynchronous communications with peripheral devices and other MCUs.
17.3 Features
Features of the SCI module include: * Full duplex operation Standard mark/space non-return-to-zero (NRZ) format 32 programmable baud rates Programmable 8-bit or 9-bit character length Separately enabled transmitter and receiver Separate receiver and transmitter CPU interrupt requests Programmable transmitter output polarity Two receiver wakeup methods: - Idle line wakeup - Address mark wakeup
NON-DISCLOSURE
* * * * * * *
Advance Information 236 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
*
Interrupt-driven operation with eight interrupt flags: - Transmitter empty - Transmission complete - Receiver full - Idle receiver input - Receiver overrun - Noise error - Framing error - Parity error
* * *
Receiver framing error detection Hardware parity checking 1/16 bit-time noise detection
17.4 Functional Description
Figure 17-1 shows the structure of the SCI module. The SCI allows full-duplex, asynchronous, NRZ serial communication between the MCU and remote devices, including other MCUs. The transmitter and receiver of the SCI operate independently, although they use the same baud rate generator. During normal operation, the CPU monitors the status of the SCI, writes the data to be transmitted, and processes received data.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 237
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
INTERNAL BUS
SCI DATA REGISTER TRANSMITTER INTERRUPT CONTROL RECEIVER INTERRUPT CONTROL RECEIVE SHIFT REGISTER ERROR INTERRUPT CONTROL
SCI DATA REGISTER TRANSMIT SHIFT REGISTER
PTE1/RxD
PTE0/TxD
TXINV SCTIE
AGREEMENT
TCIE SCRIE ILIE TE RE RWU SBK SCTE TC SCRF IDLE OR NF FE PE LOOPS LOOPS WAKEUP CONTROL RECEIVE CONTROL FLAG CONTROL M WAKE ILTY CGMXCLK /4 PRESCALER BAUD RATE GENERATOR PEN PTY DATA SELECTION CONTROL ENSCI
R8 T8
ORIE NEIE FEIE PEIE
TRANSMIT CONTROL
NON-DISCLOSURE
ENSCI
BKF RPF
/ 16
Figure 17-1. SCI Module Block Diagram
Advance Information 238 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
Table 17-1. SCI I/O Register Summary
Addr. $0013 Register Name SCI Control Register 1 (SCC1) Read: Write: Bit 7 LOOPS 6 ENSCI 5 TXINV 4 M 3 WAKE 2 ILTY 1 PEN Bit 0 PTY
$0014
SCI Control Register 2 (SCC2)
Read: Write:
SCTIE
TCIE
SCRIE
ILIE
TE
RE
RWU
SBK
$0015
Write:
R
T8
R
R
ORIE
NEIE
FEIE
PEIE
$0016
SCI Status Register 1 (SCS1)
Read: Write:
SCTE R
TC R
SCRF R
IDLE R
OR R
NF R
FE R
PE R
$0017
SCI Status Register 2 (SCS2)
Read: Write:
0 R
0 R
0 R
0 R
0 R
0 R
BKF R
RPF R
$0018
SCI Data Register (SCDR)
Read: Write:
R7 T7
R6 T6
R5 T5
R4 T4
R3 T3
R2 T2
R1 T1
R0 T0
$0019
SCI Baud Rate Register (SCBR)
Read: Write:
0 R
0 R
SCP1
SCP0
R
SCR2
SCR1
SCR0
R
= Reserved
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 239
NON-DISCLOSURE
AGREEMENT
SCI Control Register 3 (SCC3)
Read:
R8
REQUIRED
Serial Communications Interface (SCI) REQUIRED
17.4.1 Data Format The SCI uses the standard non-return-to-zero mark/space data format illustrated in Figure 17-2.
8-BIT DATA FORMAT (BIT M IN SCC1 CLEAR) START BIT
POSSIBLE PARITY BIT BIT 6 BIT 7 STOP BIT
BIT 0
BIT 1
BIT 2
BIT 3
BIT 4
BIT 5
NEXT START BIT
AGREEMENT
9-BIT DATA FORMAT (BIT M IN SCC1 SET) START BIT BIT 0 BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7
POSSIBLE PARITY BIT BIT 8 STOP BIT
NEXT START BIT
Figure 17-2. SCI Data Formats 17.4.2 Transmitter Figure 17-3 shows the structure of the SCI transmitter.
NON-DISCLOSURE
17.4.3 Character Length The transmitter can accommodate either 8-bit or 9-bit data. The state of the M bit in SCI control register 1 (SCC1) determines character length. When transmitting 9-bit data, bit T8 in SCI control register 3 (SCC3) is the ninth bit (bit 8).
Advance Information 240 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
17.4.4 Character Transmission During an SCI transmission, the transmit shift register shifts a character out to the PTE0/TxD pin. The SCI data register (SCDR) is the write-only buffer between the internal data bus and the transmit shift register. To initiate an SCI transmission: 1. Initialize the Tx and Rx rate in the SCI baud register (SCBR) ($0019) see 17.9.7 SCI Baud Rate Register. 2. Enable the SCI by writing a logic 1 to ENSCI in SCI control register 1 (SCC1) ($0013). 3. Enable the transmitter by writing a logic 1 to the transmitter enable bit (TE) in SCI control register 2 (SCC2) ($0014). 4. Clear the SCI transmitter empty bit (SCTE) by first reading SCI status register (SCS1) ($0016) and then writing to the SCDR ($0018). 5. Repeat step 3 for each subsequent transmission. At the start of a transmission, transmitter control logic automatically loads the transmit shift register with a preamble of 10 or 11 logic 1s. After the preamble shifts out, control logic transfers the SCDR data into the transmit shift register. A logic 0 start bit automatically goes into the least significant bit position of the transmit shift register. A logic 1 stop bit goes into the most significant bit position. The SCI transmitter empty bit, SCTE in the SCI status control register (SCS1), becomes set when the SCDR transfers a byte to the transmit shift register. The SCTE bit indicates that the SCDR can accept new data from the internal data bus. If the SCI transmit interrupt enable bit, SCTIE (SCC2), is also set, the SCTE bit generates a transmitter CPU interrupt request. When the transmit shift register is not transmitting a character, the PTE0/TxD pin goes to the idle condition, logic 1. If at any time software clears the ENSCI bit in SCI control register 1 (SCC1), the transmitter and receiver relinquish control of the port E pins.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 241
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
INTERNAL BUS
/4 CGMXCLK
PRESCALER
BAUD DIVIDER
/ 16
SCI DATA REGISTER
SCP1 SCP0 SCR1 SCR2 SCR0 TRANSMITTER CPU INTERRUPT REQUEST STOP
H
8
7
6
5
4
3
2
1
0
START L
11-BIT TRANSMIT SHIFT REGISTER
PTE0/TxD
AGREEMENT
TXINV
M PEN PTY PARITY GENERATION LOAD FROM SCDR
MSB
SHIFT ENABLE
T8
TRANSMITTER CONTROL LOGIC
SCTE SCTE
PREAMBLE ALL ONES
NON-DISCLOSURE
SCTIE TC TCIE
LOOPS SCTIE TC TCIE ENSCI TE
Figure 17-3. SCI Transmitter
Advance Information 242 Serial Communications Interface (SCI)
BREAK ALL ZEROS SBK
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
Table 17-2. SCI Transmitter I/O Register Summary
Addr. $0013 Register Name SCI Control Register 1 (SCC1) Read: Write: Bit 7 LOOPS 6 ENSCI 5 TXINV 4 M 3 WAKE 2 ILTY 1 PEN Bit 0 PTY
$0014
SCI Control Register 2 (SCC2)
Read: Write:
SCTIE
TCIE
SCRIE
ILIE
TE
RE
RWU
SBK
$0015
Write:
R
T8
R
R
ORIE
NEIE
FEIE
PEIE
$0016
SCI Status Register 1 (SCS1)
Read: Write:
SCTE R
TC R
SCRF R
IDLE R
OR R
NF R
FE R
PE R
$0017
SCI Status Register 2 (SCS2)
Read: Write:
0 R
0 R
0 R
0 R
0 R
0 R
BKF R
RPF R
$0018
SCI Data Register (SCDR)
Read: Write:
R7 T7
R6 T6
R5 T5
R4 T4
R3 T3
R2 T2
R1 T1
R0 T0
$0019
SCI Baud Rate Register (SCBR)
Read: Write:
0 R
0 R
SCP1
SCP0
R
SCR2
SCR1
SCR0
R
= Reserved
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 243
NON-DISCLOSURE
AGREEMENT
SCI Control Register 3 (SCC3)
Read:
R8
REQUIRED
Serial Communications Interface (SCI) REQUIRED
17.4.5 Break Characters Writing a logic 1 to the send break bit, SBK (SCC2), loads the transmit shift register with a break character. A break character contains all logic 0s and has no start, stop, or parity bit. Break character length depends on the M bit (SCC1). As long as SBK is at logic 1, transmitter logic continuously loads break characters into the transmit shift register. After software clears the SBK bit, the shift register finishes transmitting the last break character and then transmits at least one logic 1. The automatic logic 1 at the end of a break character guarantees the recognition of the start bit of the next character. The SCI recognizes a break character when a start bit is followed by eight or nine logic 0 data bits and a logic 0 where the stop bit should be. Receiving a break character has the following effects on SCI registers: * * * * * Sets the framing error bit (FE) in SCS1 Sets the SCI receiver full bit (SCRF) in SCS1 Clears the SCI data register (SCDR) Clears the R8 bit in SCC3 Sets the break flag bit (BKF) in SCS2 May set the overrun (OR), noise flag (NF), parity error (PE), or reception in progress flag (RPF) bits
NON-DISCLOSURE
AGREEMENT
*
Advance Information 244 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
17.4.6 Idle Characters An idle character contains all logic 1s and has no start, stop, or parity bit. Idle character length depends on the M bit (mode character length) in SCC1. The preamble is a synchronizing idle character that begins every transmission. If the TE bit (transmitter enable) is cleared during a transmission, the PTE0/TxD pin becomes idle after completion of the transmission in progress. Clearing and then setting the TE bit during a transmission queues an idle character to be sent after the character currently being transmitted.
NOTE:
When queueing an idle character, return the TE bit to logic 1 before the stop bit of the current character shifts out to the PTE0/TxD pin. Setting TE after the stop bit appears on PTE0/TxD causes loss of data previously written to the SCDR. A good time to toggle the TE bit is when the SCTE bit becomes set and just before writing the next byte to the SCDR.
17.4.7 Inversion of Transmitted Output The transmit inversion bit (TXINV) in SCI control register 1 (SCC1) reverses the polarity of transmitted data. All transmitted values, including idle, break, start, and stop bits, are inverted when TXINV is at logic 1. (See 17.9.1 SCI Control Register 1.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 245
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
17.4.8 Transmitter Interrupts The following conditions can generate CPU interrupt requests from the SCI transmitter: * SCI transmitter empty (SCTE) -- The SCTE bit in SCS1 indicates that the SCDR has transferred a character to the transmit shift register. SCTE can generate a transmitter CPU interrupt request. Setting the SCI transmit interrupt enable bit, SCTIE (SCC2), enables the SCTE bit to generate transmitter CPU interrupt requests. Transmission complete (TC) -- The TC bit in SCS1 indicates that the transmit shift register and the SCDR are empty and that no break or idle character has been generated. The transmission complete interrupt enable bit, TCIE (SCC2), enables the TC bit to generate transmitter CPU interrupt requests.
AGREEMENT
*
17.4.9 Receiver Figure 17-4 shows the structure of the SCI receiver.
NON-DISCLOSURE
Advance Information 246 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
INTERNAL BUS
SCR1 SCP1 SCP0 /4 CGMXCLK PTE1/RxD PRESCALER BAUD DIVIDER SCR2 SCR0 START / 16 DATA RECOVERY ALL ZEROS ALL ONES SCI DATA REGISTER
11-BIT RECEIVE SHIFT REGISTER 8 7 6 5 4 3 2 1 0
H
L
BKF RPF ERROR CPU INTERRUPT REQUEST
MSB
CPU INTERRUPT REQUEST
M WAKE ILTY PEN PTY WAKEUP LOGIC PARITY CHECKING IDLE ILIE SCRF SCRIE
SCRF IDLE
RWU
R8
ILIE
SCRIE
OR ORIE NF NEIE FE FEIE PE PEIE
OR ORIE NF NEIE FE FEIE PE PEIE
Figure 17-4. SCI Receiver Block Diagram
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 247
NON-DISCLOSURE
AGREEMENT
REQUIRED
STOP
Serial Communications Interface (SCI) REQUIRED
Table 17-3. SCI Receiver I/O Register Summary
Addr. $0013 Register Name SCI Control Register 1 (SCC1) Read: Write: Bit 7 LOOPS 6 ENSCI 5 TXINV 4 M 3 WAKE 2 ILTY 1 PEN Bit 0 PTY
$0014
SCI Control Register 2 (SCC2)
Read: Write:
SCTIE
TCIE
SCRIE
ILIE
TE
RE
RWU
SBK
AGREEMENT
$0015
SCI Control Register 3 (SCC3)
Read: Write:
R8 R
T8
R
R
ORIE
NEIE
FEIE
PEIE
$0016
SCI Status Register 1 (SCS1)
Read: Write:
SCTE R
TC R
SCRF R
IDLE R
OR R
NF R
FE R
PE R
$0017
SCI Status Register 2 (SCS2)
Read: Write:
0 R
0 R
0 R
0 R
0 R
0 R
BKF R
RPF R
$0018
SCI Data Register (SCDR)
Read: Write:
R7 T7
R6 T6
R5 T5
R4 T4
R3 T3
R2 T2
R1 T1
R0 T0
NON-DISCLOSURE
$0019
SCI Baud Rate Register (SCBR)
Read: Write:
0 R
0 R
SCP1
SCP0
R
SCR2
SCR1
SCR0
R
= Reserved
Advance Information 248 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
17.4.10 Character Length The receiver can accommodate either 8-bit or 9-bit data. The state of the M bit in SCI control register 1 (SCC1) determines character length. When receiving 9-bit data, bit R8 in SCI control register 2 (SCC2) is the ninth bit (bit 8). When receiving 8-bit data, bit R8 is a copy of the eighth bit (bit 7).
17.4.11 Character Reception During an SCI reception, the receive shift register shifts characters in from the PTE1/RxD pin. The SCI data register (SCDR) is the read-only buffer between the internal data bus and the receive shift register. After a complete character shifts into the receive shift register, the data portion of the character transfers to the SCDR. The SCI receiver full bit, SCRF, in SCI status register 1 (SCS1) becomes set, indicating that the received byte can be read. If the SCI receive interrupt enable bit, SCRIE (SCC2), is also set, the SCRF bit generates a receiver CPU interrupt request.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 249
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
17.4.12 Data Sampling The receiver samples the PTE1/RxD pin at the RT clock rate. The RT clock is an internal signal with a frequency 16 times the baud rate. To adjust for baud rate mismatch, the RT clock is resynchronized at the following times (see Figure 17-5): * * After every start bit After the receiver detects a data bit change from logic 1 to logic 0 (after the majority of data bit samples at RT8, RT9, and RT10 returns a valid logic 1 and the majority of the next RT8, RT9, and RT10 samples returns a valid logic 0)
AGREEMENT
To locate the start bit, data recovery logic does an asynchronous search for a logic 0 preceded by three logic 1s. When the falling edge of a possible start bit occurs, the RT clock begins to count to 16.
START BIT PTE1/RxD
LSB
NON-DISCLOSURE
SAMPLES
START BIT QUALIFICATION
START BIT VERIFICATION
DATA SAMPLING
RT CLOCK RT10 RT11 RT12 RT13 RT14 RT15 RT CLOCK STATE RT CLOCK RESET RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT1 RT2 RT3 RT4 RT5 RT6 RT7 RT8 RT9 RT16 RT1 RT2 RT3 RT4
Figure 17-5. Receiver Data Sampling
Advance Information 250 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Functional Description
To verify the start bit and to detect noise, data recovery logic takes samples at RT3, RT5, and RT7. Table 17-4 summarizes the results of the start bit verification samples. Table 17-4. Start Bit Verification
RT3, RT5, and RT7 Samples 000 001 010 011 100 101 110 111 Start Bit Verification Yes Yes Yes No Yes No No No Noise Flag 0 1
0 1 0 0 0
If start bit verification is not successful, the RT clock is reset and a new search for a start bit begins. To determine the value of a data bit and to detect noise, recovery logic takes samples at RT8, RT9, and RT10. Table 17-5 summarizes the results of the data bit samples. Table 17-5. Data Bit Recovery
RT8, RT9, and RT10 Samples 000 001 010 011 100 101 110 111 Data Bit Determination 0 0 0 1 0 1 1 1 Noise Flag 0 1 1 1 1 1 1 0
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 251
NON-DISCLOSURE
AGREEMENT
1
REQUIRED
Serial Communications Interface (SCI) REQUIRED
NOTE:
The RT8, RT9, and RT10 samples do not affect start bit verification. If any or all of the RT8, RT9, and RT10 start bit samples are logic 1s following a successful start bit verification, the noise flag (NF) is set and the receiver assumes that the bit is a start bit.
To verify a stop bit and to detect noise, recovery logic takes samples at RT8, RT9, and RT10. Table 17-6 summarizes the results of the stop bit samples. Table 17-6. Stop Bit Recovery
RT8, RT9, and RT10 Samples 000 001 010 011 100 101 110 111 Framing Error Flag 1 1 1 0 1 0 0 0 Noise Flag 0 1 1 1 1 1 1 0
NON-DISCLOSURE
AGREEMENT
17.4.13 Framing Errors
If the data recovery logic does not detect a logic 1 where the stop bit should be in an incoming character, it sets the framing error bit, FE, in SCS1. The FE flag is set at the same time that the SCRF bit (SCS1) is set. A break character that has no stop bit also sets the FE bit.
17.4.14 Receiver Wakeup So that the MCU can ignore transmissions intended only for other receivers in multiple-receiver systems, the receiver can be put into a standby state. Setting the receiver wakeup bit, RWU (SCC2), puts the receiver into a standby state during which receiver interrupts are disabled.
Advance Information 252 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Receiver Interrupts
Depending on the state of the WAKE bit in SCC1, either of two conditions on the PTE1/RxD pin can bring the receiver out of the standby state: * Address mark -- An address mark is a logic 1 in the most significant bit position of a received character. When the WAKE bit is set, an address mark wakes the receiver from the standby state by clearing the RWU bit. The address mark also sets the SCI receiver full bit, SCRF. Software can then compare the character containing the address mark to the user-defined address of the receiver. If they are the same, the receiver remains awake and processes the characters that follow. If they are not the same, software can set the RWU bit and put the receiver back into the standby state. Idle input line condition -- When the WAKE bit is clear, an idle character on the PTE1/RxD pin wakes the receiver from the standby state by clearing the RWU bit. The idle character that wakes the receiver does not set the receiver idle bit, IDLE, or the SCI receiver full bit, SCRF. The idle line type bit, ILTY, determines whether the receiver begins counting logic 1s as idle character bits after the start bit or after the stop bit.
*
17.5 Receiver Interrupts
The following sources can generate CPU interrupt requests from the SCI receiver: * SCI receiver full (SCRF) -- The SCRF bit in SCS1 indicates that the receive shift register has transferred a character to the SCDR. SCRF can generate a receiver CPU interrupt request. Setting the SCI receive interrupt enable bit, SCRIE (SCC2), enables the SCRF bit to generate receiver CPU interrupts.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 253
NON-DISCLOSURE
NOTE:
Clearing the WAKE bit after the PTE1/RxD pin has been idle may cause the receiver to wake up immediately.
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
* Idle input (IDLE) -- The IDLE bit in SCS1 indicates that 10 or 11 consecutive logic 1s shifted in from the PTE1/RxD pin. The idle line interrupt enable bit, ILIE (SCC2), enables the IDLE bit to generate CPU interrupt requests.
17.5.1 Error Interrupts The following receiver error flags in SCS1 can generate CPU interrupt requests: * Receiver overrun (OR) -- The OR bit indicates that the receive shift register shifted in a new character before the previous character was read from the SCDR. The previous character remains in the SCDR, and the new character is lost. The overrun interrupt enable bit, ORIE (SCC3), enables OR to generate SCI error CPU interrupt requests. Noise flag (NF) -- The NF bit is set when the SCI detects noise on incoming data or break characters, including start, data, and stop bits. The noise error interrupt enable bit, NEIE (SCC3), enables NF to generate SCI error CPU interrupt requests. Framing error (FE) -- The FE bit in SCS1 is set when a logic 0 occurs where the receiver expects a stop bit. The framing error interrupt enable bit, FEIE (SCC3), enables FE to generate SCI error CPU interrupt requests. Parity error (PE) -- The PE bit in SCS1 is set when the SCI detects a parity error in incoming data. The parity error interrupt enable bit, PEIE (SCC3), enables PE to generate SCI error CPU interrupt requests.
AGREEMENT
*
*
NON-DISCLOSURE
*
Advance Information 254 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) Low-Power Modes
17.6 Low-Power Modes
The WAIT and STOP instructions put the MCU in low-power standby modes.
17.6.1 Wait Mode The SCI module remains active after the execution of a WAIT instruction. In wait mode, the SCI module registers are not accessible by the CPU. Any enabled CPU interrupt request from the SCI module can bring the MCU out of wait mode. If SCI module functions are not required during wait mode, reduce power consumption by disabling the module before executing the WAIT instruction.
17.6.2 Stop Mode The SCI module is inactive after the execution of a STOP instruction. The STOP instruction does not affect SCI register states. SCI module operation resumes after an external interrupt. Because the internal clock is inactive during stop mode, entering stop mode during an SCI transmission or reception results in invalid data.
17.7 SCI During Break Module Interrupts
The system integration module (SIM) controls whether status bits in other modules can be cleared during interrupts generated by the break module. The BCFE bit in the SIM break flag control register (SBFCR) enables software to clear status bits during the break state. To allow software to clear status bits during a break interrupt, write a logic 1 to the BCFE bit. If a status bit is cleared during the break state, it remains cleared when the MCU exits the break state. To protect status bits during the break state, write a logic 0 to the BCFE bit. With BCFE at logic 0 (its default state), software can read and write
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 255
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
I/O registers during the break state without affecting status bits. Some status bits have a 2-step read/write clearing procedure. If software does the first step on such a bit before the break, the bit cannot change during the break state as long as BCFE is at logic 0. After the break, doing the second step clears the status bit.
17.8 I/O Signals
Port E shares two of its pins with the SCI module. The two SCI I/O pins are: * * PTE0/TxD -- Transmit data PTE1/RxD -- Receive data
AGREEMENT
17.8.1 PTE0/TxD (Transmit Data) The PTE0/TxD pin is the serial data output from the SCI transmitter. The SCI shares the PTE0/TxD pin with port E. When the SCI is enabled, the PTE0/TxD pin is an output regardless of the state of the DDRE0 bit in data direction register E (DDRE).
NON-DISCLOSURE
17.8.2 PTE1/RxD (Receive Data) The PTE1/RxD pin is the serial data input to the SCI receiver. The SCI shares the PTE1/RxD pin with port E. When the SCI is enabled, the PTE1/RxD pin is an input regardless of the state of the DDRE1 bit in data direction register E (DDRE).
Advance Information 256 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) I/O Registers
17.9 I/O Registers
These I/O registers control and monitor SCI operation: * * * * * * * SCI control register 1 (SCC1) SCI control register 2 (SCC2) SCI control register 3 (SCC3) SCI status register 1 (SCS1) SCI status register 2 (SCS2) SCI data register (SCDR) SCI baud rate register (SCBR)
17.9.1 SCI Control Register 1 SCI control register 1: * * * * * * * * Enables loop mode operation Enables the SCI Controls output polarity Controls character length Controls SCI wakeup method Controls idle character detection Enables parity function Controls parity type
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 257
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
Address:
$0013 Bit 7 6 ENSCI 0 5 TXINV 0 4 M 0 3 WAKE 0 2 ILTY 0 1 PEN 0 Bit 0 PTY 0
Read: LOOPS Write: Reset: 0
Figure 17-6. SCI Control Register 1 (SCC1) LOOPS -- Loop Mode Select Bit This read/write bit enables loop mode operation. In loop mode the PTE1/RxD pin is disconnected from the SCI, and the transmitter output goes into the receiver input. Both the transmitter and the receiver must be enabled to use loop mode. Reset clears the LOOPS bit. 1 = Loop mode enabled 0 = Normal operation enabled ENSCI -- Enable SCI Bit This read/write bit enables the SCI and the SCI baud rate generator. Clearing ENSCI sets the SCTE and TC bits in SCI status register 1 and disables transmitter interrupts. Reset clears the ENSCI bit. 1 = SCI enabled 0 = SCI disabled TXINV -- Transmit Inversion Bit This read/write bit reverses the polarity of transmitted data. Reset clears the TXINV bit. 1 = Transmitter output inverted 0 = Transmitter output not inverted
NON-DISCLOSURE
AGREEMENT
NOTE:
Setting the TXINV bit inverts all transmitted values, including idle, break, start, and stop bits.
Advance Information 258 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) I/O Registers
M -- Mode (Character Length) Bit This read/write bit determines whether SCI characters are eight or nine bits long. (See Table 17-7.) The ninth bit can serve as an extra stop bit, as a receiver wakeup signal, or as a parity bit. Reset clears the M bit. 1 = 9-bit SCI characters 0 = 8-bit SCI characters WAKE -- Wakeup Condition Bit This read/write bit determines which condition wakes up the SCI: a logic 1 (address mark) in the most significant bit position of a received character or an idle condition on the PTE1/RxD pin. Reset clears the WAKE bit. 1 = Address mark wakeup 0 = Idle line wakeup ILTY -- Idle Line Type Bit This read/write bit determines when the SCI starts counting logic 1s as idle character bits. The counting begins either after the start bit or after the stop bit. If the count begins after the start bit, then a string of logic 1s preceding the stop bit can cause false recognition of an idle character. Beginning the count after the stop bit avoids false idle character recognition, but requires properly synchronized transmissions. Reset clears the ILTY bit. 1 = Idle character bit count begins after stop bit 0 = Idle character bit count begins after start bit PEN -- Parity Enable Bit This read/write bit enables the SCI parity function. (See Table 17-7.) When enabled, the parity function inserts a parity bit in the most significant bit position. (See Figure 17-2.) Reset clears the PEN bit. 1 = Parity function enabled 0 = Parity function disabled
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 259
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
PTY -- Parity Bit This read/write bit determines whether the SCI generates and checks for odd parity or even parity. (See Table 17-7.) Reset clears the PTY bit. 1 = Odd parity 0 = Even parity
NOTE:
Changing the PTY bit in the middle of a transmission or reception can generate a parity error.
Table 17-7. Character Format Selection
Control Bits M 0 1 0 0 1 1 PEN:PTY 0X 0X 10 11 10 11 Start Bits 1 1 1 1 1 1 Character Format Data Bits 8 9 7 7 8 8 Parity None None Even Odd Even Odd Stop Bits 1 1 1 1 1 1 Character Length 10 Bits 11 Bits 10 Bits 10 Bits 11 Bits 11 Bits
NON-DISCLOSURE
Advance Information 260 Serial Communications Interface (SCI)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) I/O Registers
17.9.2 SCI Control Register 2 SCI control register 2: * Enables the following CPU interrupt requests: - Enables the SCTE bit to generate transmitter CPU interrupt requests - Enables the TC bit to generate transmitter CPU interrupt requests - Enables the SCRF bit to generate receiver CPU interrupt requests - Enables the IDLE bit to generate receiver CPU interrupt requests * * * *
Address:
Enables the transmitter Enables the receiver Enables SCI wakeup Transmits SCI break characters
$0014 Bit 7 6 TCIE 0 5 SCRIE 0 4 ILIE 0 3 TE 0 2 RE 0 1 RWU 0 Bit 0 SBK 0
Write: Reset:
SCTIE 0
Figure 17-7. SCI Control Register 2 (SCC2) SCTIE -- SCI Transmit Interrupt Enable Bit This read/write bit enables the SCTE bit to generate SCI transmitter CPU interrupt requests. Reset clears the SCTIE bit. 1 = SCTE enabled to generate CPU interrupt requests 0 = SCTE not enabled to generate CPU interrupt requests TCIE -- Transmission Complete Interrupt Enable Bit This read/write bit enables the TC bit to generate SCI transmitter CPU interrupt requests. Reset clears the TCIE bit. 1 = TC enabled to generate CPU interrupt requests 0 = TC not enabled to generate CPU interrupt requests
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI) Advance Information 261
NON-DISCLOSURE
Read:
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
SCRIE -- SCI Receive Interrupt Enable Bit This read/write bit enables the SCRF bit to generate SCI receiver CPU interrupt requests. Reset clears the SCRIE bit. 1 = SCRF enabled to generate CPU interrupt requests 0 = SCRF not enabled to generate CPU interrupt requests ILIE -- Idle Line Interrupt Enable Bit This read/write bit enables the IDLE bit to generate SCI receiver CPU interrupt requests. Reset clears the ILIE bit. 1 = IDLE enabled to generate CPU interrupt requests 0 = IDLE not enabled to generate CPU interrupt requests TE -- Transmitter Enable Bit Setting this read/write bit begins the transmission by sending a preamble of 10 or 11 logic 1s from the transmit shift register to the PTE0/TxD pin. If software clears the TE bit, the transmitter completes any transmission in progress before the PTE0/TxD returns to the idle condition (logic 1). Clearing and then setting TE during a transmission queues an idle character to be sent after the character currently being transmitted. Reset clears the TE bit. 1 = Transmitter enabled 0 = Transmitter disabled
NON-DISCLOSURE
AGREEMENT
NOTE:
Writing to the TE bit is not allowed when the enable SCI bit (ENSCI) is clear. ENSCI is in SCI control register 1.
RE -- Receiver Enable Bit Setting this read/write bit enables the receiver. Clearing the RE bit disables the receiver but does not affect receiver interrupt flag bits. Reset clears the RE bit. 1 = Receiver enabled 0 = Receiver disabled
NOTE:
Writing to the RE bit is not allowed when the enable SCI bit (ENSCI) is clear. ENSCI is in SCI control register 1.
Advance Information 262 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) I/O Registers
RWU -- Receiver Wakeup Bit This read/write bit puts the receiver in a standby state during which receiver interrupts are disabled. The WAKE bit in SCC1 determines whether an idle input or an address mark brings the receiver out of the standby state and clears the RWU bit. Reset clears the RWU bit. 1 = Standby state 0 = Normal operation SBK -- Send Break Bit Setting and then clearing this read/write bit transmits a break character followed by a logic 1. The logic 1 after the break character guarantees recognition of a valid start bit. If SBK remains set, the transmitter continuously transmits break characters with no logic 1s between them. Reset clears the SBK bit. 1 = Transmit break characters 0 = No break characters transmitted
NOTE:
Do not toggle the SBK bit immediately after setting the SCTE bit because toggling SBK too early causes the SCI to send a break character instead of a preamble.
SCI control register 3: * * Stores the ninth SCI data bit received and the ninth SCI data bit to be transmitted Enables these interrupts: - Receiver overrun interrupts - Noise error interrupts - Framing error interrupts - Parity error interrupts
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 263
NON-DISCLOSURE
17.9.3 SCI Control Register 3
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
Address:
$0015 Bit 7 6 T8 5 R 0 4 R 0 U = Unaffected 3 ORIE 0 2 NEIE 0 1 FEIE 0 Bit 0 PEIE 0
Read: Write: Reset:
R8 R U R U = Reserved
Figure 17-8. SCI Control Register 3 (SCC3)
AGREEMENT
R8 -- Received Bit 8 When the SCI is receiving 9-bit characters, R8 is the read-only ninth bit (bit 8) of the received character. R8 is received at the same time that the SCDR receives the other eight bits. When the SCI is receiving 8-bit characters, R8 is a copy of the eighth bit (bit 7). Reset has no effect on the R8 bit. T8 -- Transmitted Bit 8 When the SCI is transmitting 9-bit characters, T8 is the read/write ninth bit (bit 8) of the transmitted character. T8 is loaded into the transmit shift register at the same time that the SCDR is loaded into the transmit shift register. Reset has no effect on the T8 bit. ORIE -- Receiver Overrun Interrupt Enable Bit This read/write bit enables SCI error CPU interrupt requests generated by the receiver overrun bit, OR. 1 = SCI error CPU interrupt requests from OR bit enabled 0 = SCI error CPU interrupt requests from OR bit disabled NEIE -- Receiver Noise Error Interrupt Enable Bit This read/write bit enables SCI error CPU interrupt requests generated by the noise error bit, NE. Reset clears NEIE. 1 = SCI error CPU interrupt requests from NE bit enabled 0 = SCI error CPU interrupt requests from NE bit disabled
NON-DISCLOSURE
Advance Information 264
MC68HC08AS32 -- Rev. 3.0 Serial Communications Interface (SCI) MOTOROLA
Serial Communications Interface (SCI) I/O Registers
FEIE -- Receiver Framing Error Interrupt Enable Bit This read/write bit enables SCI error CPU interrupt requests generated by the framing error bit, FE. Reset clears FEIE. 1 = SCI error CPU interrupt requests from FE bit enabled 0 = SCI error CPU interrupt requests from FE bit disabled PEIE -- Receiver Parity Error Interrupt Enable Bit This read/write bit enables SCI receiver CPU interrupt requests generated by the parity error bit, PE. (See Figure 17-9.) Reset clears PEIE. 1 = SCI error CPU interrupt requests from PE bit enabled 0 = SCI error CPU interrupt requests from PE bit disabled
17.9.4 SCI Status Register 1 SCI status register 1 contains flags to signal the following conditions: * * * * * * * *
Address:
Transfer of SCDR data to transmit shift register complete Transmission complete Transfer of receive shift register data to SCDR complete Receiver input idle Receiver overrun Noisy data Framing error Parity error
$0016 Bit 7 6 TC R 1 = Reserved 5 SCRF R 0 4 IDLE R 0 3 OR R 0 2 NF R 0 1 FE R 0 Bit 0 PE R 0
Read: Write: Reset:
SCTE R 1 R
Figure 17-9. SCI Status Register 1 (SCS1)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 265
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
SCTE -- SCI Transmitter Empty Bit This clearable, read-only bit is set when the SCDR transfers a character to the transmit shift register. SCTE can generate an SCI transmitter CPU interrupt request. When the SCTIE bit in SCC2 is set, SCTE generates an SCI transmitter CPU interrupt request. In normal operation, clear the SCTE bit by reading SCS1 with SCTE set and then writing to SCDR. Reset sets the SCTE bit. 1 = SCDR data transferred to transmit shift register 0 = SCDR data not transferred to transmit shift register
AGREEMENT
NOTE:
Setting the TE bit for the first time also sets the SCTE bit. Setting the TE and SCTIE bits generates an SCI transmitter CPU request.
TC -- Transmission Complete Bit This read-only bit is set when the SCTE bit is set and no data, preamble, or break character is being transmitted. TC generates an SCI transmitter CPU interrupt request if the TCIE bit in SCC2 is also set. TC is cleared automatically when data, preamble, or break character is queued and ready to be sent. There may be up to 1.5 transmitter clocks of latency between queueing data, preamble, and break character and the transmission actually starting. Reset sets the TC bit. 1 = No transmission in progress 0 = Transmission in progress SCRF -- SCI Receiver Full Bit This clearable, read-only bit is set when the data in the receive shift register transfers to the SCI data register. SCRF can generate an SCI receiver CPU interrupt request. In normal operation, clear the SCRF bit by reading SCS1 with SCRF set and then reading the SCDR. Reset clears SCRF. 1 = Received data available in SCDR 0 = Data not available in SCDR IDLE -- Receiver Idle Bit This clearable, read-only bit is set when 10 or 11 consecutive logic 1s appear on the receiver input. IDLE generates an SCI error CPU interrupt request if the ILIE bit in SCC2 also is set and the DMARE bit
NON-DISCLOSURE
Advance Information 266
MC68HC08AS32 -- Rev. 3.0 Serial Communications Interface (SCI) MOTOROLA
Serial Communications Interface (SCI) I/O Registers
in SCC3 is clear. Clear the IDLE bit by reading SCS1 with IDLE set and then reading the SCDR. After the receiver is enabled, it must receive a valid character that sets the SCRF bit before an idle condition can set the IDLE bit. Also, after the IDLE bit has been cleared, a valid character must again set the SCRF bit before an idle condition can set the IDLE bit. Reset clears the IDLE bit. 1 = Receiver input idle 0 = Receiver input active (or idle since the IDLE bit was cleared) OR -- Receiver Overrun Bit This clearable, read-only bit is set when software fails to read the SCDR before the receive shift register receives the next character. The OR bit generates an SCI error CPU interrupt request if the ORIE bit in SCC3 is also set. The data in the shift register is lost, but the data already in the SCDR is not affected. Clear the OR bit by reading SCS1 with OR set and then reading the SCDR. Reset clears the OR bit. 1 = Receive shift register full and SCRF = 1 0 = No receiver overrun Software latency may allow an overrun to occur between reads of SCS1 and SCDR in the flag-clearing sequence. Figure 17-10 shows the normal flag-clearing sequence and an example of an overrun caused by a delayed flag-clearing sequence. The delayed read of SCDR does not clear the OR bit because OR was not set when SCS1 was read. Byte 2 caused the overrun and is lost. The next flag-clearing sequence reads byte 3 in the SCDR instead of byte 2. In applications that are subject to software latency or in which it is important to know which byte is lost due to an overrun, the flag-clearing routine can check the OR bit in a second read of SCS1 after reading the data register. NF -- Receiver Noise Flag Bit This clearable, read-only bit is set when the SCI detects noise on the PTE1/RxD pin. NF generates an NF CPU interrupt request if the NEIE bit in SCC3 is also set. Clear the NF bit by reading SCS1 and then reading the SCDR. Reset clears the NF bit. 1 = Noise detected 0 = No noise detected
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 267
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
FE -- Receiver Framing Error Bit This clearable, read-only bit is set when a logic 0 is accepted as the stop bit. FE generates an SCI error CPU interrupt request if the FEIE bit in SCC3 also is set. Clear the FE bit by reading SCS1 with FE set and then reading the SCDR. Reset clears the FE bit. 1 = Framing error detected 0 = No framing error detected PE -- Receiver Parity Error Bit
AGREEMENT
This clearable, read-only bit is set when the SCI detects a parity error in incoming data. PE generates a PE CPU interrupt request if the PEIE bit in SCC3 is also set. Clear the PE bit by reading SCS1 with PE set and then reading the SCDR. Reset clears the PE bit. 1 = Parity error detected 0 = No parity error detected
NORMAL FLAG CLEARING SEQUENCE SCRF = 1 SCRF = 0 SCRF = 1 SCRF = 0 SCRF = 1 SCRF = 0 BYTE 4 READ SCS1 SCRF = 1 OR = 0 READ SCDR BYTE 3 BYTE 4 READ SCS1 SCRF = 1 OR = 1 READ SCDR BYTE 3
BYTE 1
BYTE 2 READ SCS1 SCRF = 1 OR = 0 READ SCDR BYTE 1 READ SCS1 SCRF = 1 OR = 0 READ SCDR BYTE 2
BYTE 3
NON-DISCLOSURE
DELAYED FLAG CLEARING SEQUENCE SCRF = 1 SCRF = 1 OR = 1 SCRF = 0 OR = 1 SCRF = 1 OR = 1 SCRF = 0 OR = 0
BYTE 1
BYTE 2 READ SCS1 SCRF = 1 OR = 0 READ SCDR BYTE 1
BYTE 3
Figure 17-10. Flag Clearing Sequence
Advance Information 268 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) I/O Registers
17.9.5 SCI Status Register 2 SCI status register 2 contains flags to signal two conditions: 1. Break character detected 2. Incoming data
Address: $0017 Bit 7 Read: R Write: Reset: 0 R 0 = Reserved 0 0 0 0 R R R R R R 0 R 0 6 5 4 3 2 1 BKF Bit 0 RPF
Figure 17-11. SCI Status Register 2 (SCS2) BKF -- Break Flag Bit This clearable, read-only bit is set when the SCI detects a break character on the PTE1/RxD pin. In SCS1, the FE and SCRF bits are also set. In 9-bit character transmissions, the R8 bit in SCC3 is cleared. BKF does not generate a CPU interrupt request. Clear BKF by reading SCS2 with BKF set and then reading the SCDR. Once cleared, BKF can become set again only after logic 1s again appear on the PTE1/RxD pin followed by another break character. Reset clears the BKF bit. 1 = Break character detected 0 = No break character detected RPF -- Reception in Progress Flag Bit This read-only bit is set when the receiver detects a logic 0 during the RT1 time period of the start bit search. RPF does not generate an interrupt request. RPF is reset after the receiver detects false start bits, usually from noise or a baud rate mismatch or when the receiver detects an idle character. Polling RPF before disabling the SCI module or entering stop mode can show whether a reception is in progress. 1 = Reception in progress 0 = No reception in progress
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI) Advance Information 269
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
17.9.6 SCI Data Register The SCI data register is the buffer between the internal data bus and the receive and transmit shift registers. Reset has no effect on data in the SCI data register.
Address: $0018 Bit 7 Read: R7 T7 6 R6 T6 5 R5 T5 4 R4 T4 3 R3 T3 2 R2 T2 1 R1 T1 Bit 0 R0 T0
AGREEMENT
Write: Reset:
Unaffected by Reset
Figure 17-12. SCI Data Register (SCDR) R7/T7-R0/T0 -- Receive/Transmit Data Bits Reading address $0018 accesses the read-only received data bits, R7-R0. Writing to address $0018 writes the data to be transmitted, T7-T0. Reset has no effect on the SCI data register.
NON-DISCLOSURE
Advance Information 270 Serial Communications Interface (SCI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Communications Interface (SCI) I/O Registers
17.9.7 SCI Baud Rate Register The baud rate register selects the baud rate for both the receiver and the transmitter.
Address: $0019 Bit 7 Read: R Write: Reset: 0 R 0 = Reserved 0 0 0 0 0 0 R SCP1 SCP0 R SCR2 SCR1 SCR0 6 5 4 3 2 1 Bit 0
Figure 17-13. SCI BAUD Rate Register 1 (SCBR) SCP1 and SCP0 -- SCI Baud Rate Prescaler Bits These read/write bits select the baud rate prescaler divisor as shown in Table 17-8. Reset clears SCP1 and SCP0. Table 17-8. SCI Baud Rate Prescaling
SCP1:SCP0 00 01 10 11 Prescaler Divisor (PD)
3 4 13
SCR2-SCR0 -- SCI Baud Rate Select Bits These read/write bits select the SCI baud rate divisor as shown in Table 17-9. Reset clears SCR2:SCR0.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
Advance Information 271
NON-DISCLOSURE
1
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED
Table 17-9. SCI Baud Rate Selection
SCR2:SCR1:SCR0 000 001 010 011 100 Baud Rate Divisor (BD) 1 2 4 8 16 32 64 128
AGREEMENT
101 110 111
Use the following formula to calculate the SCI baud rate: CGMXCLK Baud rate = ----------------------------------64 x PD x BD PD = Prescale divisor (see Table 17-8) BD = Baud rate divisor (see Table 17-9) Table 17-10 shows the SCI baud rates that can be generated with a 4.194-MHz crystal.
NON-DISCLOSURE
Advance Information 272
MC68HC08AS32 -- Rev. 3.0 Serial Communications Interface (SCI) MOTOROLA
Serial Communications Interface (SCI) I/O Registers
Table 17-10. SCI Baud Rate Selection Examples
SCP1:SCP0 00 00 00 00 00 00 00 00 01 01 01 01 01 01 01 01 10 10 10 10 10 10 10 10 11 11 11 11 11 11 11 11 Prescaler Divisor (PD) 1 1 1 1 1 1 1 1 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 13 13 13 13 13 13 13 13 SCR2:SCR1:SCR0 000 001 010 011 100 101 110 111 000 001 010 011 100 101 110 111 000 001 010 011 100 101 110 111 000 001 010 011 100 101 110 111 Baud Rate Divisor (BD) 1 2 4 8 16 32 64 128 1 2 4 8 16 32 64 128 1 2 4 8 16 32 64 128 1 2 4 8 16 32 64 128 Baud Rate (fXCLK = 4.194 MHz) 65,531 32,766 16,383 8191 4095 2048 1024 512 21,844 10,922 5461 2730 1365 683 341 171 16,383
4096 2048 1024 512 256 128 5041 1664 1260 630 315 158 78.8 39.4 Advance Information
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Communications Interface (SCI)
273
NON-DISCLOSURE
8191
AGREEMENT
REQUIRED
Serial Communications Interface (SCI) REQUIRED NON-DISCLOSURE
Advance Information 274 Serial Communications Interface (SCI)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 18. Serial Peripheral Interface (SPI)
18.1 Contents
18.2 18.3 18.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 Pin Name and Register Name Conventions . . . . . . . . . . . . . .277
18.5 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278 18.5.1 Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 18.5.2 Slave Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281 18.6 Transmission Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 18.6.1 Clock Phase and Polarity Controls . . . . . . . . . . . . . . . . . .282 18.6.2 Transmission Format When CPHA = 0 . . . . . . . . . . . . . . .283 18.6.3 Transmission Format When CPHA = 1 . . . . . . . . . . . . . . .284 18.6.4 Transmission Initiation Latency . . . . . . . . . . . . . . . . . . . . .286 18.7 Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288 18.7.1 Overflow Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288 18.7.2 Mode Fault Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290 18.8 18.9 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292 Queuing Transmission Data . . . . . . . . . . . . . . . . . . . . . . . . . .293
18.10 Resetting the SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 18.11 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 18.11.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 18.11.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 18.12 SPI During Break Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . .297 18.13 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298 18.13.1 MISO (Master In/Slave Out) . . . . . . . . . . . . . . . . . . . . . . .298 18.13.2 MOSI (Master Out/Slave In) . . . . . . . . . . . . . . . . . . . . . . .299
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI) Advance Information 275
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
18.13.3 18.13.4 18.13.5 SPSCK (Serial Clock) . . . . . . . . . . . . . . . . . . . . . . . . . . . .299 SS (Slave Select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 VSS (Clock Ground) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301
18.14 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301 18.14.1 SPI Control Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302 18.14.2 SPI Status and Control Register . . . . . . . . . . . . . . . . . . . .304 18.14.3 SPI Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308
AGREEMENT
18.2 Introduction
This section describes the serial peripheral interface (SPI) module, which allows full-duplex, synchronous, serial communications with peripheral devices.
18.3 Features
Features of the SPI module include: * * Full-duplex operation Master mode and slave mode Double-buffered operation with separate transmit and receive registers Four master mode frequencies (maximum = bus frequency / 2) Maximum slave mode frequency = bus frequency Serial clock with programmable polarity and phase Two separately enabled interrupts with CPU service: - SPRF (SPI receiver full) - SPTE (SPI transmitter empty) * * * * Mode fault error flag with cpu interrupt capability Overflow error flag with CPU interrupt capability Programmable wired-OR mode I2C (inter-integrated circuit) compatibility
NON-DISCLOSURE
* * * * *
Advance Information 276 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) Pin Name and Register Name Conventions
18.4 Pin Name and Register Name Conventions
The generic names of the SPI input/output (I/O) pins are: * * * * SS (slave select) SPSCK (SPI serial clock) MOSI (master out/slave in) MISO (master in/slave out)
Table 18-1. Pin Name Conventions
SPI Generic Pin Name: Full SPI Pin Name: MISO PTE5/MISO MOSI PTE6/MOSI SS PTE4/SS SPSCK PTE7/SPSCK
The generic names of the SPI I/O registers are: * * * SPI control register (SPCR) SPI status and control register (SPSCR) SPI data register (SPDR)
Table 18-2 shows the names and the addresses of the SPI I/O registers. Table 18-2. I/O Register Addresses
Register Name SPI Control Register SPI Status and Control Register SPI Data Register Address $0010 $0011 $0012
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 277
NON-DISCLOSURE
AGREEMENT
The SPI shares four I/O pins with a parallel I/O port. The full name of an SPI pin reflects the name of the shared port pin. Table 18-1 shows the full names of the SPI I/O pins. The generic pin names appear in the text that follows.
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED 18.5 Functional Description
Table 18-3 summarizes the SPI I/O registers and Figure 18-1 shows the structure of the SPI module. Table 18-3. SPI I/O Register Summary
Addr $0010 Register Name Bit 7 6 R 0 5 SPMSTR 1 4 CPOL 0 3 CPHA 1 2 SPWOM 0 1 SPE 0 Bit 0 SPTIE 0
AGREEMENT
SPI Control Register Read: SPRIE (SPCR) Write: Reset: 0
$0011
SPI Status and Control Register Read: (SPSCR) Write: Reset:
SPRF ERRIE R 0 0
OVRF R 0
MODF R 0
SPTE MODFEN R 1 0 0 0 SPR1 SPR0
$0012
SPI Data Register Read: (SPDR) Write: Reset:
R7 T7
R6 T6
R5 T5
R4 T4
R3 T3
R2 T2
R1 T1
R0 T0
Unaffected by Reset R = Reserved
NON-DISCLOSURE
Advance Information 278
MC68HC08AS32 -- Rev. 3.0 Serial Peripheral Interface (SPI) MOTOROLA
Serial Peripheral Interface (SPI) Functional Description
INTERNAL BUS
TRANSMIT DATA REGISTER
BUS CLOCK 7 /2 CLOCK DIVIDER /8 / 32 / 128 CLOCK SELECT 6
SHIFT REGISTER 5 4 3 2 1 0 MISO
MOSI RECEIVE DATA REGISTER PIN CONTROL LOGIC SPSCK CLOCK LOGIC M S SS
SPMSTR
SPE
SPR1
SPR0
SPMSTR
CPHA
CPOL
TRANSMITTER CPU INTERRUPT REQUEST SPI CONTROL RECEIVER/ERROR CPU INTERRUPT REQUEST
MODFEN ERRIE SPTIE SPRIE SPE SPRF SPTE OVRF MODF
SPWOM
Figure 18-1. SPI Module Block Diagram The SPI module allows full-duplex, synchronous, serial communication between the MCU and peripheral devices, including other MCUs. Software can poll the SPI status flags or SPI operation can be interrupt-driven. All SPI interrupts can be serviced by the CPU. The following paragraphs describe the operation of the SPI module.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 279
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
18.5.1 Master Mode The SPI operates in master mode when the SPI master bit, SPMSTR (SPCR $0010), is set.
NOTE:
Configure the SPI modules as master and slave before enabling them. Enable the master SPI before enabling the slave SPI. Disable the slave SPI before disabling the master SPI. (See 18.14.1 SPI Control Register.)
Only a master SPI module can initiate transmissions. Software begins the transmission from a master SPI module by writing to the SPI data register. If the shift register is empty, the byte immediately transfers to the shift register, setting the SPI transmitter empty bit, SPTE (SPSCR $0011). The byte begins shifting out on the MOSI pin under the control of the serial clock. (See Figure 18-2.) The SPR1 and SPR0 bits control the baud rate generator and determine the speed of the shift register. (See 18.14.2 SPI Status and Control Register.) Through the SPSCK pin, the baud rate generator of the master also controls the shift register of the slave peripheral.
NON-DISCLOSURE
AGREEMENT
MASTER MCU
SLAVE MCU
SHIFT REGISTER
MISO
MISO
MOSI
MOSI SHIFT REGISTER
SPSCK BAUD RATE GENERATOR
SPSCK
SS
VDD
SS
Figure 18-2. Full-Duplex Master-Slave Connections
Advance Information 280 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) Functional Description
As the byte shifts out on the MOSI pin of the master, another byte shifts in from the slave on the master's MISO pin. The transmission ends when the receiver full bit, SPRF (SPSCR), becomes set. At the same time that SPRF becomes set, the byte from the slave transfers to the receive data register. In normal operation, SPRF signals the end of a transmission. Software clears SPRF by reading the SPI status and control register and then reading the SPI data register. Writing to the SPI data register clears the SPTE bit.
The SPI operates in slave mode when the SPMSTR bit (SPCR $0010) is clear. In slave mode the SPSCK pin is the input for the serial clock from the master MCU. Before a data transmission occurs, the SS pin of the slave MCU must be at logic 0. SS must remain low until the transmission is complete. (See 18.7.2 Mode Fault Error.) In a slave SPI module, data enters the shift register under the control of the serial clock from the master SPI module. After a byte enters the shift register of a slave SPI, it is transferred to the receive data register, and the SPRF bit (SPSCR) is set. To prevent an overflow condition, slave software then must read the SPI data register before another byte enters the shift register. The maximum frequency of the SPSCK for an SPI configured as a slave is the bus clock speed, which is twice as fast as the fastest master SPSCK clock that can be generated. The frequency of the SPSCK for an SPI configured as a slave does not have to correspond to any SPI baud rate. The baud rate only controls the speed of the SPSCK generated by an SPI configured as a master. Therefore, the frequency of the SPSCK for an SPI configured as a slave can be any frequency less than or equal to the bus speed. When the master SPI starts a transmission, the data in the slave shift register begins shifting out on the MISO pin. The slave can load its shift register with a new byte for the next transmission by writing to its transmit data register. The slave must write to its transmit data register at least one bus cycle before the master starts the next transmission. Otherwise, the byte already in the slave shift register shifts out on the MISO pin.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI) Advance Information 281
NON-DISCLOSURE
AGREEMENT
18.5.2 Slave Mode
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
Data written to the slave shift register during a a transmission remains in a buffer until the end of the transmission. When the clock phase bit (CPHA) is set, the first edge of SPSCK starts a transmission. When CPHA is clear, the falling edge of SS starts a transmission. (See 18.6 Transmission Formats.) If the write to the data register is late, the SPI transmits the data already in the shift register from the previous transmission.
AGREEMENT
NOTE:
To prevent SPSCK from appearing as a clock edge, SPSCK must be in the proper idle state before the slave is enabled.
18.6 Transmission Formats
During an SPI transmission, data is simultaneously transmitted (shifted out serially) and received (shifted in serially). A serial clock line synchronizes shifting and sampling on the two serial data lines. A slave select line allows individual selection of a slave SPI device; slave devices that are not selected do not interfere with SPI bus activities. On a master SPI device, the slave select line can be used optionally to indicate a multiple-master bus contention.
NON-DISCLOSURE
18.6.1 Clock Phase and Polarity Controls Software can select any of four combinations of serial clock (SCK) phase and polarity using two bits in the SPI control register (SPCR). The clock polarity is specified by the CPOL control bit, which selects an active high or low clock and has no significant effect on the transmission format. The clock phase (CPHA) control bit (SPCR) selects one of two fundamentally different transmission formats. The clock phase and polarity should be identical for the master SPI device and the communicating slave device. In some cases, the phase and polarity are changed between transmissions to allow a master device to communicate with peripheral slaves having different requirements.
NOTE:
Before writing to the CPOL bit or the CPHA bit (SPCR), disable the SPI by clearing the SPI enable bit (SPE).
MC68HC08AS32 -- Rev. 3.0 Serial Peripheral Interface (SPI) MOTOROLA
Advance Information 282
Serial Peripheral Interface (SPI) Transmission Formats
18.6.2 Transmission Format When CPHA = 0 Figure 18-3 shows an SPI transmission in which CPHA (SPCR) is logic 0. The figure should not be used as a replacement for data sheet parametric information.Two waveforms are shown for SCK: one for CPOL = 0 and another for CPOL = 1. The diagram may be interpreted as a master or slave timing diagram since the serial clock (SCK), master in/slave out (MISO), and master out/slave in (MOSI) pins are directly connected between the master and the slave. The MISO signal is the output from the slave, and the MOSI signal is the output from the master. The SS line is the slave select input to the slave. The slave SPI drives its MISO output only when its slave select input (SS) is at logic 0, so that only the selected slave drives to the master. The SS pin of the master is not shown but is assumed to be inactive. The SS pin of the master must be high or must be reconfigured as general-purpose I/O not affecting the SPI. (See 18.7.2 Mode Fault Error.) When CPHA = 0, the first SPSCK edge is the MSB capture strobe. Therefore, the slave must begin driving its data before the first SPSCK edge, and a falling edge on the SS pin is used to start the transmission. The SS pin must be toggled high and then low again between each byte transmitted as shown in Figure 18-4.
SCK CYCLE # FOR REFERENCE SCK CPOL = 0
1
2
3
4
5
6
7
8
SCK CPOL = 1 MOSI FROM MASTER MISO FROM SLAVE SS TO SLAVE CAPTURE STROBE
MSB
BIT 6
BIT 5
BIT 4
BIT 3
BIT 2
BIT 1
LSB
MSB
BIT 6
BIT 5
BIT 4
BIT 3
BIT 2
BIT 1
LSB
Figure 18-3. Transmission Format (CPHA = 0)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 283
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
MISO/MOSI MASTER SS SLAVE SS CPHA = 0 SLAVE SS CPHA = 1
BYTE 1
BYTE 2
BYTE 3
Figure 18-4. CPHA/SS Timing When CPHA = 0 for a slave, the falling edge of SS indicates the beginning of the transmission. This causes the SPI to leave its idle state and begin driving the MISO pin with the MSB of its data. Once the transmission begins, no new data is allowed into the shift register from the transmit data register. Therefore, the SPI data register of the slave must be loaded with transmit data before the falling edge of SS. Any data written after the falling edge is stored in the transmit data register and transferred to the shift register after the current transmission.
AGREEMENT
18.6.3 Transmission Format When CPHA = 1 Figure 18-5 shows an SPI transmission in which CPHA (SPCR) is logic 1. The figure should not be used as a replacement for data sheet parametric information. Two waveforms are shown for SCK: one for CPOL = 0 and another for CPOL = 1. The diagram may be interpreted as a master or slave timing diagram since the serial clock (SCK), master in/slave out (MISO), and master out/slave in (MOSI) pins are directly connected between the master and the slave. The MISO signal is the output from the slave, and the MOSI signal is the output from the master. The SS line is the slave select input to the slave. The slave SPI drives its MISO output only when its slave select input (SS) is at logic 0, so that only the selected slave drives to the master. The SS pin of the master is not shown but is assumed to be inactive. The SS pin of the master must be high or must be reconfigured as general-purpose I/O not affecting the SPI. (See 18.7.2 Mode Fault Error.) When CPHA = 1, the master
NON-DISCLOSURE
Advance Information 284
MC68HC08AS32 -- Rev. 3.0 Serial Peripheral Interface (SPI) MOTOROLA
Serial Peripheral Interface (SPI) Transmission Formats
SCK CYCLE # FOR REFERENCE
1
2
3
4
5
6
7
8
SCK CPOL = 0
SCK CPOL =1
MOSI FROM MASTER MISO FROM SLAVE
MSB
BIT 6
BIT 5
BIT 4
BIT 3
BIT 2
BIT 1
LSB
MSB
BIT 6
BIT 5
BIT 4
BIT 3
BIT 2
BIT 1
LSB
SS TO SLAVE
CAPTURE STROBE
Figure 18-5. Transmission Format (CPHA = 1) begins driving its MOSI pin on the first SPSCK edge. Therefore, the slave uses the first SPSCK edge as a start transmission signal. The SS pin can remain low between transmissions. This format may be preferable in systems having only one master and only one slave driving the MISO data line. When CPHA = 1 for a slave, the first edge of the SPSCK indicates the beginning of the transmission. This causes the SPI to leave its idle state and begin driving the MISO pin with the MSB of its data. Once the transmission begins, no new data is allowed into the shift register from the transmit data register. Therefore, the SPI data register of the slave must be loaded with transmit data before the first edge of SPSCK. Any data written after the first edge is stored in the transmit data register and transferred to the shift register after the current transmission.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 285
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
18.6.4 Transmission Initiation Latency When the SPI is configured as a master (SPMSTR = 1), transmissions are started by a software write to the SPDR ($0012). CPHA has no effect on the delay to the start of the transmission, but it does affect the initial state of the SCK signal. When CPHA = 0, the SCK signal remains inactive for the first half of the first SCK cycle. When CPHA = 1, the first SCK cycle begins with an edge on the SCK line from its inactive to its active level. The SPI clock rate (selected by SPR1-SPR0) affects the delay from the write to SPDR and the start of the SPI transmission. (See Figure 18-6.) The internal SPI clock in the master is a free-running derivative of the internal MCU clock. It is only enabled when both the SPE and SPMSTR bits (SPCR) are set to conserve power. SCK edges occur halfway through the low time of the internal MCU clock. Since the SPI clock is free-running, it is uncertain where the write to the SPDR will occur relative to the slower SCK. This uncertainty causes the variation in the initiation delay shown in Figure 18-6. This delay will be no longer than a single SPI bit time. That is, the maximum delay between the write to SPDR and the start of the SPI transmission is two MCU bus cycles for DIV2, eight MCU bus cycles for DIV8, 32 MCU bus cycles for DIV32, and 128 MCU bus cycles for DIV128.
NON-DISCLOSURE
Advance Information 286 Serial Peripheral Interface (SPI)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) Transmission Formats
WRITE TO SPDR BUS CLOCK MOSI SCK CPHA = 1 SCK CPHA = 0 SCK CYCLE NUMBER
INITIATION DELAY
MSB
BIT 6
BIT 5
INITIATION DELAY FROM WRITE SPDR TO TRANSFER BEGIN
WRITE TO SPDR BUS CLOCK EARLIEST LATEST WRITE TO SPDR BUS CLOCK EARLIEST WRITE TO SPDR BUS CLOCK EARLIEST WRITE TO SPDR BUS CLOCK EARLIEST SCK = INTERNAL CLOCK / 128; 128 POSSIBLE START POINTS LATEST SCK = INTERNAL CLOCK / 32; 32 POSSIBLE START POINTS LATEST SCK = INTERNAL CLOCK / 8; 8 POSSIBLE START POINTS LATEST SCK = INTERNAL CLOCK / 2; 2 POSSIBLE START POINTS
Figure 18-6. Transmission Start Delay (Master)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 287
NON-DISCLOSURE
AGREEMENT
1
2
3
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED 18.7 Error Conditions
Two flags signal SPI error conditions: 1. Overflow (OVRFin SPSCR) -- Failing to read the SPI data register before the next byte enters the shift register sets the OVRF bit. The new byte does not transfer to the receive data register, and the unread byte still can be read by accessing the SPI data register. OVRF is in the SPI status and control register. 2. Mode fault error (MODF in SPSCR) -- The MODF bit indicates that the voltage on the slave select pin (SS) is inconsistent with the mode of the SPI. MODF is in the SPI status and control register.
AGREEMENT
18.7.1 Overflow Error The overflow flag (OVRF in SPSCR) becomes set if the SPI receive data register still has unread data from a previous transmission when the capture strobe of bit 1 of the next transmission occurs. (See Figure 18-3 and Figure 18-5.) If an overflow occurs, the data being received is not transferred to the receive data register so that the unread data can still be read. Therefore, an overflow error always indicates the loss of data. OVRF generates a receiver/error CPU interrupt request if the error interrupt enable bit (ERRIE in SPSCR) is also set. MODF and OVRF can generate a receiver/error CPU interrupt request. (See Figure 18-9.) It is not possible to enable only MODF or OVRF to generate a receiver/error CPU interrupt request. However, leaving MODFEN low prevents MODF from being set. If an end-of-block transmission interrupt was meant to pull the MCU out of wait, having an overflow condition without overflow interrupts enabled causes the MCU to hang in wait mode. If the OVRF is enabled to generate an interrupt, it can pull the MCU out of wait mode instead. If the CPU SPRF interrupt is enabled and the OVRF interrupt is not, watch for an overflow condition. Figure 18-7 shows how it is possible to miss an overflow.
NON-DISCLOSURE
Advance Information 288
MC68HC08AS32 -- Rev. 3.0 Serial Peripheral Interface (SPI) MOTOROLA
Serial Peripheral Interface (SPI) Error Conditions
BYTE 1 1
BYTE 2 4
BYTE 3 6
BYTE 4 8
SPRF OVRF READ SPSCR READ SPDR 1 2 3 4 2 5
3 BYTE 1 SETS SPRF BIT. CPU READS SPSCR WITH SPRF BIT SET AND OVRF BIT CLEAR. CPU READS BYTE 1 IN SPDR, CLEARING SPRF BIT. BYTE 2 SETS SPRF BIT. 5 6 7 8
7 CPU READS SPSCR WITH SPRF BIT SET AND OVRF BIT CLEAR. BYTE 3 SETS OVRF BIT. BYTE 3 IS LOST. CPU READS BYTE 2 IN SPDR, CLEARING SPRF BIT, BUT NOT OVRF BIT. BYTE 4 FAILS TO SET SPRF BIT BECAUSE OVRF BIT IS SET. BYTE 4 IS LOST.
Figure 18-7. Missed Read of Overflow Condition The first part of Figure 18-7 shows how to read the SPSCR and SPDR to clear the SPRF without problems. However, as illustrated by the second transmission example, the OVRF flag can be set in between the time that SPSCR and SPDR are read. In this case, an overflow can be easily missed. Since no more SPRF interrupts can be generated until this OVRF is serviced, it will not be obvious that bytes are being lost as more transmissions are completed. To prevent this, either enable the OVRF interrupt or do another read of the SPSCR after the read of the SPDR. This ensures that the OVRF was not set before the SPRF was cleared and that future transmissions will complete with an SPRF interrupt. Figure 18-8 illustrates this process. Generally, to avoid this second SPSCR read, enable the OVRF to the CPU by setting the ERRIE bit (SPSCR).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 289
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
BYTE 1 SPI RECEIVE COMPLETE SPRF 1
BYTE 2 5
BYTE 3 7
BYTE 4 11
OVRF 2 4 6 9 8 8 9 12 14
READ SPSCR
READ SPDR
3 1 2 3 4 5 6 7 BYTE 1 SETS SPRF BIT. CPU READS SPSCR WITH SPRF BIT SET AND OVRF BIT CLEAR. CPU READS BYTE 1 IN SPDR, CLEARING SPRF BIT. CPU READS SPSCR AGAIN TO CHECK OVRF BIT. BYTE 2 SETS SPRF BIT. CPU READS SPSCR WITH SPRF BIT SET AND OVRF BIT CLEAR. BYTE 3 SETS OVRF BIT. BYTE 3 IS LOST.
10
13
AGREEMENT
CPU READS BYTE 2 IN SPDR, CLEARING SPRF BIT. CPU READS SPSCR AGAIN TO CHECK OVRF BIT.
10 CPU READS BYTE 2 SPDR, CLEARING OVRF BIT. 11 BYTE 4 SETS SPRF BIT. 12 CPU READS SPSCR. 13 CPU READS BYTE 4 IN SPDR, CLEARING SPRF BIT. 14 CPU READS SPSCR AGAIN TO CHECK OVRF BIT.
Figure 18-8. Clearing SPRF When OVRF Interrupt Is Not Enabled
NON-DISCLOSURE
18.7.2 Mode Fault Error For the MODF flag (in SPSCR) to be set, the mode fault error enable bit (MODFEN in SPSCR) must be set. Clearing the MODFEN bit does not clear the MODF flag but does prevent MODF from being set again after MODF is cleared. MODF generates a receiver/error CPU interrupt request if the error interrupt enable bit (ERRIE in SPSCR) is also set. The SPRF, MODF, and OVRF interrupts share the same CPU interrupt vector. MODF and OVRF can generate a receiver/error CPU interrupt request. (See Figure 18-9.) It is not possible to enable only MODF or OVRF to generate a receiver/error CPU interrupt request. However, leaving MODFEN low prevents MODF from being set.
Advance Information 290 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) Error Conditions
In a master SPI with the mode fault enable bit (MODFEN) set, the mode fault flag (MODF) is set if SS goes to logic 0. A mode fault in a master SPI causes the following events to occur: * * * * * If ERRIE = 1, the SPI generates an SPI receiver/error CPU interrupt request. The SPE bit is cleared. The SPTE bit is set. The SPI state counter is cleared. The data direction register of the shared I/O port regains control of port drivers.
NOTE:
To prevent bus contention with another master SPI after a mode fault error, clear all data direction register (DDR) bits associated with the SPI shared port pins. Setting the MODF flag (SPSCR) does not clear the SPMSTR bit. Reading SPMSTR when MODF = 1 will indicate that a MODE fault error occurred in either master mode or slave mode.
When configured as a slave (SPMSTR = 0), the MODF flag is set if SS goes high during a transmission. When CPHA = 0, a transmission begins when SS goes low and ends once the incoming SPSCK returns to its idle level after the shift of the eighth data bit. When CPHA = 1, the transmission begins when the SPSCK leaves its idle level and SS is already low. The transmission continues until the SPSCK returns to its IDLE level after the shift of the last data bit. (See 18.6 Transmission Formats.)
NOTE:
NOTE:
When CPHA = 0, a MODF occurs if a slave is selected (SS is at logic 0) and later unselected (SS is at logic 1) even if no SPSCK is sent to that slave. This happens because SS at logic 0 indicates the start of the transmission (MISO driven out with the value of MSB) for CPHA = 0. When CPHA = 1, a slave can be selected and then later unselected with no transmission occurring. Therefore, MODF does not occur since a transmission was never begun.
In a slave SPI (MSTR = 0), the MODF bit generates an SPI receiver/error CPU interrupt request if the ERRIE bit is set. The MODF
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 291
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
bit does not clear the SPE bit or reset the SPI in any way. Software can abort the SPI transmission by toggling the SPE bit of the slave.
NOTE:
A logic 1 voltage on the SS pin of a slave SPI puts the MISO pin in a high impedance state. Also, the slave SPI ignores all incoming SPSCK clocks, even if a transmission has begun.
To clear the MODF flag, read the SPSCR and then write to the SPCR register. This entire clearing procedure must occur with no MODF condition existing or else the flag will not be cleared.
AGREEMENT
18.8 Interrupts
Four SPI status flags can be enabled to generate CPU interrupt requests, as shown in Table 18-4. Table 18-4. SPI Interrupts
Flag SPTE (Transmitter Empty) SPRF (Receiver Full) Request SPI Transmitter CPU Interrupt Request (SPTIE = 1) SPI Receiver CPU Interrupt Request (SPRIE = 1) SPI Receiver/Error Interrupt Request (ERRIE = 1) SPI Receiver/Error Interrupt Request (ERRIE = 1, MODFEN = 1)
NON-DISCLOSURE
OVRF (Overflow) MODF (Mode Fault)
The SPI transmitter interrupt enable bit (SPTIE) enables the SPTE flag to generate transmitter CPU interrupt requests. The SPI receiver interrupt enable bit (SPRIE) enables the SPRF bit to generate receiver CPU interrupt, provided that the SPI is enabled (SPE = 1). The error interrupt enable bit (ERRIE) enables both the MODF and OVRF flags to generate a receiver/error CPU interrupt request. The mode fault enable bit (MODFEN) can prevent the MODF flag from being set so that only the OVRF flag is enabled to generate receiver/error CPU interrupt requests.
Advance Information 292 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) Queuing Transmission Data
SPTE
SPTIE
SPE SPI TRANSMITTER CPU INTERRUPT REQUEST
SPRIE
SPRF
ERRIE MODF OVRF
SPI RECEIVER/ERROR CPU INTERRUPT REQUEST
Figure 18-9. SPI Interrupt Request Generation Two sources in the SPI status and control register can generate CPU interrupt requests: 1. SPI receiver full bit (SPRF) -- The SPRF bit becomes set every time a byte transfers from the shift register to the receive data register. If the SPI receiver interrupt enable bit, SPRIE, is also set, SPRF can generate an SPI receiver/error CPU interrupt request. 2. SPI transmitter empty (SPTE) -- The SPTE bit becomes set every time a byte transfers from the transmit data register to the shift register. If the SPI transmit interrupt enable bit, SPTIE, is also set, SPTE can generate an SPTE CPU interrupt request.
18.9 Queuing Transmission Data
The double-buffered transmit data register allows a data byte to be queued and transmitted. For an SPI configured as a master, a queued data byte is transmitted immediately after the previous transmission has completed. The SPI transmitter empty flag (SPTE in SPSCR) indicates when the transmit data buffer is ready to accept new data. Write to the SPI data register only when the SPTE bit is high. Figure 18-10 shows the timing associated with doing back-to-back transmissions with the SPI (SPSCK has CPHA-CPOL = 1-0).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 293
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
WRITE TO SPDR
1
3
8
SPTE
2
5
10
SPSCK (CPHA:CPOL = 1:0) MOSI MSB BIT BIT BIT BIT BIT BIT LSB MSB BIT BIT BIT BIT BIT BIT LSB MSB BIT BIT BIT 654321 654321 654 BYTE 1 BYTE 2 BYTE 3 4 9
SPRF
AGREEMENT
READ SPSCR
6
11
READ SPDR 1 2 3 4 CPU WRITES BYTE 1 TO SPDR, CLEARING SPTE BIT. BYTE 1 TRANSFERS FROM TRANSMIT DATA REGISTER TO SHIFT REGISTER, SETTING SPTE BIT. CPU WRITES BYTE 2 TO SPDR, QUEUEING BYTE 2 AND CLEARING SPTE BIT. FIRST INCOMING BYTE TRANSFERS FROM SHIFT REGISTER TO RECEIVE DATA REGISTER, SETTING SPRF BIT. BYTE 2 TRANSFERS FROM TRANSMIT DATA REGISTER TO SHIFT REGISTER, SETTING SPTE BIT. CPU READS SPSCR WITH SPRF BIT SET. 7 8 9
7 CPU READS SPDR, CLEARING SPRF BIT. CPU WRITES BYTE 3 TO SPDR, QUEUEING BYTE 3 AND CLEARING SPTE BIT.
12
SECOND INCOMING BYTE TRANSFERS FROM SHIFT REGISTER TO RECEIVE DATA REGISTER, SETTING SPRF BIT.
10 BYTE 3 TRANSFERS FROM TRANSMIT DATA REGISTER TO SHIFT REGISTER, SETTING SPTE BIT. 11 CPU READS SPSCR WITH SPRF BIT SET. 12 CPU READS SPDR, CLEARING SPRF BIT.
5 6
NON-DISCLOSURE
Figure 18-10. SPRF/SPTE CPU Interrupt Timing The transmit data buffer allows back-to-back transmissions without the slave precisely timing its writes between transmissions as in a system with a single data buffer. Also, if no new data is written to the data buffer, the last value contained in the shift register is the next data word to be transmitted. For an idle master or idle slave that has no data loaded into its transmit buffer, the SPTE is set again no more than two bus cycles after the transmit buffer empties into the shift register. This allows the user to queue up a 16-bit value to send. For an already active slave, the load of the shift register cannot occur until the transmission is completed. This implies that a back-to-back write to the transmit data register is not possible. The SPTE indicates when the next write can occur.
Advance Information 294 Serial Peripheral Interface (SPI) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) Resetting the SPI
18.10 Resetting the SPI
Any system reset completely resets the SPI. Partial resets occur whenever the SPI enable bit (SPE) is low. Whenever SPE is low, the following occurs: * * * * * The SPTE flag is set. Any transmission currently in progress is aborted. The shift register is cleared.
All the SPI port logic is defaulted back to being general-purpose I/O.
These additional items are reset only by a system reset: * * * All control bits in the SPCR register All control bits in the SPSCR register (MODFEN, ERRIE, SPR1, and SPR0) The status flags SPRF, OVRF, and MODF
By not resetting the SPRF, OVRF, and MODF flags, the user can still service these interrupts after the SPI has been disabled. The user can disable the SPI by writing 0 to the SPE bit. The SPI also can be disabled by a mode fault occurring in an SPI that was configured as a master with the MODFEN bit set.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 295
NON-DISCLOSURE
By not resetting the control bits when SPE is low, the user can clear SPE between transmissions without having to reset all control bits when SPE is set back to high for the next transmission.
AGREEMENT
The SPI state counter is cleared, making it ready for a new complete transmission.
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED 18.11 Low-Power Modes
The WAIT and STOP instructions put the MCU in low-power standby modes.
18.11.1 Wait Mode The SPI module remains active after the execution of a WAIT instruction. In wait mode, the SPI module registers are not accessible by the CPU. Any enabled CPU interrupt request from the SPI module can bring the MCU out of wait mode. If SPI module functions are not required during wait mode, reduce power consumption by disabling the SPI module before executing the WAIT instruction. To exit wait mode when an overflow condition occurs, enable the OVRF bit to generate CPU interrupt requests by setting the error interrupt enable bit (ERRIE). (See 18.8 Interrupts.)
AGREEMENT
18.11.2 Stop Mode
NON-DISCLOSURE
The SPI module is inactive after the execution of a STOP instruction. The STOP instruction does not affect register conditions. SPI operation resumes after the MCU exits stop mode. If stop mode is exited by reset, any transfer in progress is aborted and the SPI is reset.
Advance Information 296 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) SPI During Break Interrupts
18.12 SPI During Break Interrupts
The system integration module (SIM) controls whether status bits in other modules can be cleared during the break state. The BCFE bit in the SIM break flag control register (SBFCR, $FE03) enables software to clear status bits during the break state. (See 9.8.3 SIM Break Flag Control Register.) To allow software to clear status bits during a break interrupt, write a logic 1 to the BCFE bit. If a status bit is cleared during the break state, it remains cleared when the MCU exits the break state. To protect status bits during the break state, write a logic 0 to the BCFE bit. With BCFE at logic 0 (its default state), software can read and write I/O registers during the break state without affecting status bits. Some status bits have a 2-step read/write clearing procedure. If software does the first step on such a bit before the break, the bit cannot change during the break state as long as BCFE is at logic 0. After the break, doing the second step clears the status bit. Since the SPTE bit cannot be cleared during a break with the BCFE bit cleared, a write to the data register in break mode will not initiate a transmission nor will this data be transferred into the shift register. Therefore, a write to the SPDR in break mode with the BCFE bit cleared has no effect.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 297
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED 18.13 I/O Signals
The SPI module has five I/O pins and shares four of them with a parallel I/O port. * * * * MISO -- Data received MOSI -- Data transmitted SPSCK -- Serial clock SS -- Slave select VSS -- Clock ground
AGREEMENT
*
The SPI has limited inter-integrated circuit (I2C) capability (requiring software support) as a master in a single-master environment. To communicate with I2C peripherals, MOSI becomes an open-drain output when the SPWOM bit in the SPI control register is set. In I2C communication, the MOSI and MISO pins are connected to a bidirectional pin from the I2C peripheral and through a pullup resistor to VDD.
18.13.1 MISO (Master In/Slave Out)
NON-DISCLOSURE
MISO is one of the two SPI module pins that transmit serial data. In full duplex operation, the MISO pin of the master SPI module is connected to the MISO pin of the slave SPI module. The master SPI simultaneously receives data on its MISO pin and transmits data from its MOSI pin. Slave output data on the MISO pin is enabled only when the SPI is configured as a slave. The SPI is configured as a slave when its SPMSTR bit is logic 0 and its SS pin is at logic 0. To support a multiple-slave system, a logic 1 on the SS pin puts the MISO pin in a high-impedance state. When enabled, the SPI controls data direction of the MISO pin regardless of the state of the data direction register of the shared I/O port.
Advance Information 298 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) I/O Signals
18.13.2 MOSI (Master Out/Slave In) MOSI is one of the two SPI module pins that transmit serial data. In full duplex operation, the MOSI pin of the master SPI module is connected to the MOSI pin of the slave SPI module. The master SPI simultaneously transmits data from its MOSI pin and receives data on its MISO pin. When enabled, the SPI controls data direction of the MOSI pin regardless of the state of the data direction register of the shared I/O port.
18.13.3 SPSCK (Serial Clock) The serial clock synchronizes data transmission between master and slave devices. In a master MCU, the SPSCK pin is the clock output. In a slave MCU, the SPSCK pin is the clock input. In full-duplex operation, the master and slave MCUs exchange a byte of data in eight serial clock cycles. When enabled, the SPI controls data direction of the SPSCK pin regardless of the state of the data direction register of the shared I/O port.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 299
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
18.13.4 SS (Slave Select) The SS pin has various functions depending on the current state of the SPI. For an SPI configured as a slave, the SS is used to select a slave. For CPHA = 0, the SS is used to define the start of a transmission. (See 18.6 Transmission Formats.) Since it is used to indicate the start of a transmission, the SS must be toggled high and low between each byte transmitted for the CPHA = 0 format. However, it can remain low throughout the transmission for the CPHA = 1 format. See Figure 18-11.
AGREEMENT
MISO/MOSI MASTER SS SLAVE SS CPHA = 0 SLAVE SS CPHA = 1
BYTE 1
BYTE 2
BYTE 3
Figure 18-11. CPHA/SS Timing When an SPI is configured as a slave, the SS pin is always configured as an input. It cannot be used as a general-purpose I/O regardless of the state of the MODFEN control bit. However, the MODFEN bit can still prevent the state of the SS from creating a MODF error. (See 18.14.2 SPI Status and Control Register.)
NON-DISCLOSURE
NOTE:
A logic 1 voltage on the SS pin of a slave SPI puts the MISO pin in a high-impedance state. The slave SPI ignores all incoming SPSCK clocks, even if a transmission already has begun.
When an SPI is configured as a master, the SS input can be used in conjunction with the MODF flag to prevent multiple masters from driving MOSI and SPSCK. (See 18.7.2 Mode Fault Error.) For the state of the SS pin to set the MODF flag, the MODFEN bit in the SPSCK register must be set. If the MODFEN bit is low for an SPI master, the SS pin can be used as a general-purpose I/O under the control of the data direction register of the shared I/O port. With MODFEN high, it is an input-only pin to the SPI regardless of the state of the data direction register of the shared I/O port.
Advance Information 300 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) I/O Registers
The CPU can always read the state of the SS pin by configuring the appropriate pin as an input and reading the data register. (See Table 18-5.) Table 18-5. SPI Configuration
SPE SPMSTR MODFEN 0 1 1 1 X 0 1 1 X X 0 1 SPI Configuration Not Enabled Slave Master without MODF Master with MODF State of SS Logic General-Purpose I/O; SS Ignored by SPI Input-Only to SPI General-Purpose I/O; SS Ignored by SPI Input-Only to SPI
X = don't care
18.13.5 VSS (Clock Ground) VSS is the ground return for the serial clock pin, SPSCK, and the ground for the port output buffers. To reduce the ground return path loop and minimize radio frequency (RF) emissions, connect the ground pin of the slave to the VSS pin.
18.14 I/O Registers
Three registers control and monitor SPI operation: * * * SPI control register (SPCR, $0010) SPI status and control register (SPSCR, $0011) SPI data register (SPDR, $0012)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 301
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
18.14.1 SPI Control Register The SPI control register: * * * * * *
Address:
Enables SPI module interrupt requests Selects CPU interrupt requests Configures the SPI module as master or slave Selects serial clock polarity and phase Configures the SPSCK, MOSI, and MISO pins as open-drain outputs Enables the SPI module
$0010 Bit 7 6 R 0 = Reserved 5 SPMSTR 1 4 CPOL 0 3 CPHA 1 2 SPWOM 0 1 SPE 0 Bit 0 SPTIE 0
AGREEMENT
Read: SPRIE Write: Reset: 0 R
NON-DISCLOSURE
Figure 18-12. SPI Control Register (SPCR) SPRIE -- SPI Receiver Interrupt Enable Bit This read/write bit enables CPU interrupt requests generated by the SPRF bit. The SPRF bit is set when a byte transfers from the shift register to the receive data register. Reset clears the SPRIE bit. 1 = SPRF CPU interrupt requests enabled 0 = SPRF CPU interrupt requests disabled SPMSTR -- SPI Master Bit This read/write bit selects master mode operation or slave mode operation. Reset sets the SPMSTR bit. 1 = Master mode 0 = Slave mode
Advance Information 302 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) I/O Registers
CPOL -- Clock Polarity Bit This read/write bit determines the logic state of the SPSCK pin between transmissions. (See Figure 18-3 and Figure 18-5.) To transmit data between SPI modules, the SPI modules must have identical CPOL bits. Reset clears the CPOL bit. CPHA -- Clock Phase Bit This read/write bit controls the timing relationship between the serial clock and SPI data. (See Figure 18-3 and Figure 18-5.) To transmit data between SPI modules, the SPI modules must have identical CPHA bits. When CPHA = 0, the SS pin of the slave SPI module must be set to logic 1 between bytes. (See Figure 18-11.) Reset sets the CPHA bit. When CPHA = 0 for a slave, the falling edge of SS indicates the beginning of the transmission. This causes the SPI to leave its idle state and begin driving the MISO pin with the MSB of its data. Once the transmission begins, no new data is allowed into the shift register from the data register. Therefore, the slave data register must be loaded with the desired transmit data before the falling edge of SS. Any data written after the falling edge is stored in the data register and transferred to the shift register at the current transmission. When CPHA = 1 for a slave, the first edge of the SPSCK indicates the beginning of the transmission. The same applies when SS is high for a slave. The MISO pin is held in a high-impedance state, and the incoming SPSCK is ignored. In certain cases, it may also cause the MODF flag to be set. (See 18.7.2 Mode Fault Error.) A logic 1 on the SS pin does not in any way affect the state of the SPI state machine. SPWOM -- SPI Wired-OR Mode Bit This read/write bit disables the pullup devices on pins SPSCK, MOSI, and MISO so that those pins become open-drain outputs. 1 = Wired-OR SPSCK, MOSI, and MISO pins 0 = Normal push-pull SPSCK, MOSI, and MISO pins
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 303
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
SPE -- SPI Enable Bit This read/write bit enables the SPI module. Clearing SPE causes a partial reset of the SPI. (See 18.10 Resetting the SPI.) Reset clears the SPE bit. 1 = SPI module enabled 0 = SPI module disabled SPTIE-- SPI Transmit Interrupt Enable Bit This read/write bit enables CPU interrupt requests generated by the SPTE bit. SPTE is set when a byte transfers from the transmit data register to the shift register. Reset clears the SPTIE bit. 1 = SPTE CPU interrupt requests enabled 0 = SPTE CPU interrupt requests disabled
AGREEMENT
18.14.2 SPI Status and Control Register The SPI status and control register contains flags to signal the following conditions: * * Receive data register full Failure to clear SPRF bit before next byte is received (overflow error) Inconsistent logic level on SS pin (mode fault error) Transmit data register empty
NON-DISCLOSURE
* *
The SPI status and control register also contains bits that perform these functions: * * * Enable error interrupts Enable mode fault error detection Select master SPI baud rate
Advance Information 304 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Serial Peripheral Interface (SPI) I/O Registers
Address:
$0011 Bit 7 6 ERRIE 5 OVRF R 0 = Reserved 0 4 MODF R 0 3 SPTE MODFEN R 1 0 0 0 SPR1 SPR0 2 1 Bit 0
Read: Write: Reset:
SPRF R 0 R
Figure 18-13. SPI Status and Control Register (SPSCR) SPRF -- SPI Receiver Full Bit This clearable, read-only flag is set each time a byte transfers from the shift register to the receive data register. SPRF generates a CPU interrupt request if the SPRIE bit in the SPI control register is set also. During an SPRF CPU interrupt, the CPU clears SPRF by reading the SPI status and control register with SPRF set and then reading the SPI data register. Any read of the SPI data register clears the SPRF bit, and reset also clears the SPRF bit. 1 = Receive data register full 0 = Receive data register not full ERRIE -- Error Interrupt Enable Bit This bit enables the MODF and OVRF flags to generate CPU interrupt requests. Reset clears the ERRIE bit. 1 = MODF and OVRF can generate CPU interrupt requests 0 = MODF and OVRF cannot generate CPU interrupt requests OVRF -- Overflow Bit This clearable, read-only flag is set if software does not read the byte in the receive data register before the next byte enters the shift register. In an overflow condition, the byte already in the receive data register is unaffected, and the byte that shifted in last is lost. Clear the OVRF bit by reading the SPI status and control register with OVRF set and then reading the SPI data register. Reset clears the OVRF flag. 1 = Overflow 0 = No overflow
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 305
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
MODF -- Mode Fault Bit This clearable, ready-only flag is set in a slave SPI if the SS pin goes high during a transmission. In a master SPI, the MODF flag is set if the SS pin goes low at any time. Clear the MODF bit by reading the SPI status and control register with MODF set and then writing to the SPI control register. Reset clears the MODF bit. 1 = SS pin at inappropriate logic level 0 = SS pin at appropriate logic level SPTE -- SPI Transmitter Empty Bit This clearable, read-only flag is set each time the transmit data register transfers a byte into the shift register. SPTE generates an SPTE CPU interrupt request if the SPTIE bit in the SPI control register is set also.
AGREEMENT
NOTE:
Do not write to the SPI data register unless the SPTE bit is high.
For an idle master or idle slave that has no data loaded into its transmit buffer, the SPTE will be set again within two bus cycles since the transmit buffer empties into the shift register. This allows the user to queue up a 16-bit value to send. For an already active slave, the load of the shift register cannot occur until the transmission is completed. This implies that a back-to-back write to the transmit data register is not possible. The SPTE indicates when the next write can occur. Reset sets the SPTE bit. 1 = Transmit data register empty 0 = Transmit data register not empty MODFEN -- Mode Fault Enable Bit This read/write bit, when set to 1, allows the MODF flag to be set. If the MODF flag is set, clearing the MODFEN does not clear the MODF flag. If the SPI is enabled as a master and the MODFEN bit is low, then the SS pin is available as a general-purpose I/O. If the MODFEN bit is set, then this pin is not available as a general-purpose I/O. When the SPI is enabled as a slave, the SS pin is not available as a general-purpose I/O regardless of the value of MODFEN. (See 18.13.4 SS (Slave Select).)
NON-DISCLOSURE
Advance Information 306
MC68HC08AS32 -- Rev. 3.0 Serial Peripheral Interface (SPI) MOTOROLA
Serial Peripheral Interface (SPI) I/O Registers
If the MODFEN bit is low, the level of the SS pin does not affect the operation of an enabled SPI configured as a master. For an enabled SPI configured as a slave, having MODFEN low only prevents the MODF flag from being set. It does not affect any other part of SPI operation. (See 18.7.2 Mode Fault Error.) SPR1 and SPR0 -- SPI Baud Rate Select Bits In master mode, these read/write bits select one of four baud rates as shown in Table 18-6. SPR1 and SPR0 have no effect in slave mode. Reset clears SPR1 and SPR0. Table 18-6. SPI Master Baud Rate Selection
SPR1:SPR0 00 01 10 11 Baud Rate Divisor (BD) 2 8 32 128
Use this formula to calculate the SPI baud rate: CGMOUT Baud rate = ------------------------2 x BD where: CGMOUT = base clock output of the clock generator module (CGM), see Section 8. Clock Generator Module (CGM). BD = baud rate divisor
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Serial Peripheral Interface (SPI)
Advance Information 307
NON-DISCLOSURE
AGREEMENT
REQUIRED
Serial Peripheral Interface (SPI) REQUIRED
18.14.3 SPI Data Register The SPI data register is the read/write buffer for the receive data register and the transmit data register. Writing to the SPI data register writes data into the transmit data register. Reading the SPI data register reads data from the receive data register. The transmit data and receive data registers are separate buffers that can contain different values. See Figure 18-1.
Address: $0012 Bit 7 Read: Write: Reset: R7 T7 6 R6 T6 5 R5 T5 4 R4 T4 3 R3 T3 2 R2 T2 1 R1 T1 Bit 0 R0 T0
AGREEMENT
Unaffected by Reset
Figure 18-14. SPI Data Register (SPDR) R7-R0/T7-T0 -- Receive/Transmit Data Bits
NOTE:
Do not use read-modify-write instructions on the SPI data register since the buffer read is not the same as the buffer written.
NON-DISCLOSURE
Advance Information 308 Serial Peripheral Interface (SPI)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 19. Analog-to-Digital Converter (ADC)
19.1 Contents
19.2 19.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
19.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 19.4.1 ADC Port I/O Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311 19.4.2 Voltage Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 19.4.3 Conversion Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 19.4.4 Continuous Conversion Mode . . . . . . . . . . . . . . . . . . . . . .313 19.4.5 Accuracy and Precision. . . . . . . . . . . . . . . . . . . . . . . . . . .313 19.5 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
19.7 I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 19.7.1 ADC Analog Power Pin (VDDA/VDDAREF)/ADC Voltage Reference Pin (VREFH) . . . . . . . . . . . . . . . . . .314 19.7.2 ADC Analog Ground Pin (VSSA)/ADC Voltage Reference Low Pin (VREFL). . . . . . . . . . . . . . .314 19.7.3 ADC Voltage In (ADCVIN). . . . . . . . . . . . . . . . . . . . . . . . .315 19.8 I/O Registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315 19.8.1 ADC Status and Control Register . . . . . . . . . . . . . . . . . . .315 19.8.2 ADC Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318 19.8.3 ADC Input Clock Register . . . . . . . . . . . . . . . . . . . . . . . . .318
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Analog-to-Digital Converter (ADC)
Advance Information 309
NON-DISCLOSURE
19.6 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 19.6.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 19.6.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
AGREEMENT
REQUIRED
Analog-to-Digital Converter (ADC) REQUIRED 19.2 Introduction
This section describes the 8-bit analog-to-digital converter (ADC).
19.3 Features
Features of the ADC module include: * 15 channels (52-PLCC) with multiplexed input Linear successive approximation 8-bit resolution Single or continuous conversion Conversion complete flag or conversion complete interrupt Selectable ADC clock
AGREEMENT
* * * * *
19.4 Functional Description
Fifteen ADC channels are available for sampling external sources at pins PTD6/ATD14/TCLK-PTD0/ATD8 and PTB7/ATD7-PTB0/ATD0. An analog multiplexer allows the single ADC converter to select one of the 15 ADC channels as ADC voltage input (ADCVIN). ADCVIN is converted by the successive approximation register-based counters. When the conversion is completed, ADC places the result in the ADC data register and sets a flag or generates an interrupt. (See Figure 19-1.)
NON-DISCLOSURE
Advance Information 310
MC68HC08AS32 -- Rev. 3.0 Analog-to-Digital Converter (ADC) MOTOROLA
Analog-to-Digital Converter (ADC) Functional Description
INTERNAL DATA BUS READ DDRB/DDRB WRITE DDRB/DDRD RESET WRITE PTB/PTD DDRBx/DDRDx PTBx/PTDx DISABLE
PTBx/PTDx ADC CHANNEL x
READ PTB/PTD
DISABLE ADC DATA REGISTER
INTERRUPT LOGIC
CONVERSION COMPLETE
ADC
ADC VOLTAGE IN ADCVIN
CHANNEL SELECT
ADCH[4:0]
AIEN
COCO ADC CLOCK CGMXCLK BUS CLOCK
CLOCK GENERATOR
ADIV[2:0]
ADICLK
Figure 19-1. ADC Block Diagram
19.4.1 ADC Port I/O Pins PTD6/ATD14/TCLK-PTD0/ATD8 and PTB7/ATD7-PTB0/ATD0 are general-purpose I/O pins that are shared with the ADC channels. The channel select bits (ADC status control register, $0038), define which ADC channel/port pin will be used as the input signal. The ADC overrides the port I/O logic by forcing that pin as input to the ADC. The remaining ADC channels/port pins are controlled by the port I/O logic and can be used as general-purpose I/O. Writes to the port register or DDR will not have any affect on the port pin that is selected by the ADC.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Analog-to-Digital Converter (ADC) Advance Information 311
NON-DISCLOSURE
AGREEMENT
REQUIRED
Analog-to-Digital Converter (ADC) REQUIRED
Read of a port pin which is in use by the ADC will return a logic 0 if the corresponding DDR bit is at logic 0. If the DDR bit is at logic 1, the value in the port data latch is read.
NOTE:
Do not use ADC channel ATD14 when using the PTD6/ATD14/TCLK pin as the clock input for the TIM.
19.4.2 Voltage Conversion When the input voltage to the ADC equals VREFH (see 21.7 ADC Characteristics), the ADC converts the signal to $FF (full scale). If the input voltage equals VSSA/VREFL the ADC converts it to $00. Input voltages between VREFH and VSSA/VREFL are a straight-line linear conversion. All other input voltages will result in $FF if greater than VREFH and $00 if less than VSSA/VREFL.
AGREEMENT
NOTE:
Input voltage should not exceed the analog supply voltages.
19.4.3 Conversion Time Sixteen ADC internal clocks are required to perform one conversion. The ADC starts a conversion on the first rising edge of the ADC internal clock immediately following a write to the ADSCR. If the ADC internal clock is selected to run at 1 MHz, then one conversion will take 16 s to complete. But since the ADC can run almost completely asynchronously to the bus clock, (for example, the ADC is configured to derive its internal clock from CGMXCLK and the bus clock is being derived from the PLL within the CGM [CGMOUT]), this 16-s conversion can take up to 17 s to complete. This worst-case could occur if the write to the ADSCR happened directly after the rising edge of the ADC internal clock causing the conversion to wait until the next rising edge of the ADC internal clock. With a 1-MHz ADC internal clock, the maximum sample rate is 59 kHz to 62 kHz. Refer to 21.7 ADC Characteristics 16 to 17 ADC Clock Cycles Conversion Time = ADC Clock Frequency Number of Bus Cycles = Conversion Time x Bus Frequency
Advance Information 312 Analog-to-Digital Converter (ADC) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
NON-DISCLOSURE
Analog-to-Digital Converter (ADC) Interrupts
19.4.4 Continuous Conversion Mode In the continuous conversion mode, the ADC continuously converts the selected channel, filling the ADC data register with new data after each conversion. Data from the previous conversion will be overwritten whether that data has been read or not. Conversions will continue until the ADCO bit is cleared. The COCO bit (ADC status control register, $0038) is set after each conversion and can be cleared by writing the ADC status and control register or reading of the ADC data register.
19.4.5 Accuracy and Precision The conversion process is monotonic and has no missing codes. See 21.7 ADC Characteristics for accuracy information.
19.5 Interrupts
When the AIEN bit is set, the ADC module is capable of generating a CPU interrupt after each ADC conversion. A CPU interrupt is generated if the COCO bit is at logic 0. The COCO bit is not used as a conversion complete flag when interrupts are enabled.
19.6 Low-Power Modes
The following subsections describe the low-power modes.
19.6.1 Wait Mode The ADC continues normal operation during wait mode. Any enabled CPU interrupt request from the ADC can bring the MCU out of wait mode. If the ADC is not required to bring the MCU out of wait mode, power down the ADC by setting the ADCH[4:0] bits in the ADC status and control register to logic 1s before executing the WAIT instruction.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Analog-to-Digital Converter (ADC)
Advance Information 313
NON-DISCLOSURE
AGREEMENT
REQUIRED
Analog-to-Digital Converter (ADC) REQUIRED
19.6.2 Stop Mode The ADC module is inactive after the execution of a STOP instruction. Any pending conversion is aborted. ADC conversions resume when the MCU exits stop mode. Allow one conversion cycle to stabilize the analog circuitry before attempting a new ADC conversion after exiting stop mode.
19.7 I/O Signals AGREEMENT
The ADC module has 15 channels that are shared with I/O ports B and D and one channel with an input-only port bit on port D. Refer to 21.7 ADC Characteristics for voltages referenced in the next three subsections.
19.7.1 ADC Analog Power Pin (VDDA/VDDAREF)/ADC Voltage Reference Pin (VREFH) The ADC analog portion uses VDDA/VDDAREF as its power pin. Connect the VDDA/VDDAREF pin to the same voltage potential as VDD. External filtering may be necessary to ensure clean VDDA/VDDAREF for good results. VREFH is the high reference voltage for all analog-to-digital conversions. Connect the VREFH pin to a voltage potential between 1.5 volts and VDDAREF/VDDA depending on the desired upper conversion boundary.
NON-DISCLOSURE
NOTE:
Route VDDA/VDDAREF carefully for maximum noise immunity and place bypass capacitors as close as possible to the package.
19.7.2 ADC Analog Ground Pin (VSSA)/ADC Voltage Reference Low Pin (VREFL) The ADC analog portion uses VSSA as its ground pin. Connect the VSSA pin to the same voltage potential as VSS. VREFL is the lower reference supply for the ADC.
Advance Information 314 Analog-to-Digital Converter (ADC)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Analog-to-Digital Converter (ADC) I/O Registers
19.7.3 ADC Voltage In (ADCVIN) ADCVIN is the input voltage signal from one of the 15 ADC channels to the ADC module.
19.8 I/O Registers
These I/O registers control and monitor ADC operation: * * * ADC status and control register (ADSCR) ADC data register (ADR) ADC input clock register (ADICLK)
19.8.1 ADC Status and Control Register The following paragraphs describe the function of the ADC status and control register.
Address: $0038 Bit 7 Read: Write: Reset: COCO AIEN R 0 R 0 = Reserved 0 1 1 1 1 1 ADCO ADCH4 ADCH3 ADCH2 ADCH1 ADCH0 6 5 4 3 2 1 Bit 0
Figure 19-2. ADC Status and Control Register (ADSCR) COCO -- Conversions Complete Bit When the AIEN bit is a logic 0, the COCO is a read-only bit which is set each time a conversion is completed. This bit is cleared whenever the ADC status and control register is written or whenever the ADC data register is read. Reset clears this bit.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Analog-to-Digital Converter (ADC)
Advance Information 315
NON-DISCLOSURE
AGREEMENT
REQUIRED
Analog-to-Digital Converter (ADC) REQUIRED
When the AIEN bit is a logic 1, the COCO bit selects CPU interrupts when clear. COCO does not get set after each conversion while AIEN = 1. 1 = conversion completed (AIEN = 0) 0 = conversion not completed (AIEN = 0) or 0 = CPU interrupt enabled (AIEN = 1) AIEN -- ADC Interrupt Enable Bit When this bit is set, an interrupt is generated at the end of an ADC conversion. The interrupt signal is cleared when the data register is read or the status/control register is written. Reset clears the AIEN bit. 1 = ADC interrupt enabled 0 = ADC interrupt disabled ADCO -- ADC Continuous Conversion Bit When set, the ADC will convert samples continuously and update the ADR register at the end of each conversion. Only one conversion is allowed when this bit is cleared. Reset clears the ADCO bit. 1 = Continuous ADC conversion 0 = One ADC conversion ADCH[4:0] -- ADC Channel Select Bits ADCH4, ADCH3, ADCH2, ADCH1, and ADCH0 form a 5-bit field which is used to select one of the ADC channels. The five channel select bits are detailed in Table 19-1. Care should be taken when using a port pin as both an analog and a digital input simultaneously to prevent switching noise from corrupting the analog signal. (See Table 19-1.) The ADC subsystem is turned off when the channel select bits are all set to one. This feature allows for reduced power consumption for the MCU when the ADC is not used. Reset sets all of these bits to a logic 1.
NON-DISCLOSURE
AGREEMENT
NOTE:
Recovery from the disabled state requires one conversion cycle to stabilize.
Advance Information 316 Analog-to-Digital Converter (ADC)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Analog-to-Digital Converter (ADC) I/O Registers
Table 19-1. Mux Channel Select
ADCH4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ADCH3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 ADCH2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 ADCH1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 ADCH0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 Input Select PTB0/ATD0 PTB1/ATD1 PTB2/ATD2 PTB3/ATD3 PTB4/ATD4 PTB5/ATD5
PTB7/ATD7 PTD0/ATD8 PTD1/ATD9 PTD2/ATD10 PTD3/ATD11 PTD4/ATD12 PTD5/ATD13 PTD6/ATD14/TCLK Unused(1)
Range 01111 ($0F) to 11010 ($1A) 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 0 1 1 1 0 1 0 1
Reserved VREFH(2) VSSA/VREFL(2) ADC Power Off
1. If any unused channels are selected, the resulting ADC conversion will be unknown. 2. The voltage levels supplied from internal reference nodes as specified in the table are used to verify the operation of the ADC converter both in production test and for user applications.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Analog-to-Digital Converter (ADC)
Advance Information 317
NON-DISCLOSURE
Unused(1)
AGREEMENT
PTB6/ATD6
REQUIRED
Analog-to-Digital Converter (ADC) REQUIRED
19.8.2 ADC Data Register One 8-bit data register is provided. This register is updated each time an ADC conversion completes.
Address: $0039 Bit 7 Read: Write: Reset: R = Reserved AD7 R 6 AD6 R 5 AD5 R 4 AD4 R 3 AD3 R 2 AD2 R 1 AD1 R Bit 0 AD0 R
AGREEMENT
Unaffected by Reset
Figure 19-3. ADC Data Register (ADR)
19.8.3 ADC Input Clock Register This register selects the clock frequency for the ADC.
Address: $003A Bit 7 6 ADIV1 0 = Reserved 5 ADIV0 0 4 ADICLK R
0
3 0
2 0 R 0
1 0 R 0
Bit 0 0 R 0
NON-DISCLOSURE
Read: ADIV2 Write: Reset: 0
0
R
Figure 19-4. ADC Input Clock Register (ADICLK) ADIV2:ADIV0 -- ADC Clock Prescaler Bits ADIV2, ADIV1, and ADIV0 form a 3-bit field which selects the divide ratio used by the ADC to generate the internal ADC clock. Table 19-2 shows the available clock configurations. The ADC clock should be set to approximately 1 MHz.
Advance Information 318 Analog-to-Digital Converter (ADC)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Analog-to-Digital Converter (ADC) I/O Registers
Table 19-2. ADC Clock Divide Ratio
ADIV2 0 0 0 0 1 ADIV1 0 0 1 1 X ADIV0 0 1 0 1 X ADC Clock Rate ADC Input Clock / 1 ADC Input Clock / 2 ADC Input Clock / 4 ADC Input Clock / 8 ADC Input Clock / 16
X = Don't Care
ADICLK -- ADC Input Clock Register Bit ADICLK selects either bus clock or CGMXCLK as the input clock source to generate the internal ADC clock. Reset selects CGMXCLK as the ADC clock source. If the external clock (CGMXCLK) is equal to or greater than 1 MHz, CGMXCLK can be used as the clock source for the ADC. If CGMXCLK is less than 1 MHz, use the PLL-generated bus clock as the clock source. As long as the internal ADC clock is at approximately 1 MHz, correct operation can be guaranteed. (See 21.7 ADC Characteristics.) 1 = Internal bus clock 0 = External clock (CGMXCLK) fXCLK or Bus Frequency 1 MHz = ADIV[2:0]
NOTE:
During the conversion process, changing the ADC clock will result in an incorrect conversion.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Analog-to-Digital Converter (ADC)
Advance Information 319
NON-DISCLOSURE
AGREEMENT
REQUIRED
Analog-to-Digital Converter (ADC) REQUIRED NON-DISCLOSURE
Advance Information 320 Analog-to-Digital Converter (ADC)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 20. Byte Data Link Controller-Digital (BDLC-D)
20.1 Contents
20.2 20.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323
20.4 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324 20.4.1 BDLC Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . .326 20.4.1.1 Power Off Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 20.4.1.2 Reset Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 20.4.1.3 Run Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327 20.4.1.4 BDLC Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328 20.4.1.5 BDLC Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328 20.4.1.6 Digital Loopback Mode. . . . . . . . . . . . . . . . . . . . . . . . . .328 20.4.1.7 Analog Loopback Mode . . . . . . . . . . . . . . . . . . . . . . . . .329 20.5 BDLC MUX Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329 20.5.1 Rx Digital Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330 20.5.1.1 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330 20.5.1.2 Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331 20.5.2 J1850 Frame Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . .332 20.5.3 J1850 VPW Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . .335 20.5.4 J1850 VPW Valid/Invalid Bits and Symbols . . . . . . . . . . .338 20.5.5 Message Arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343 20.6 BDLC Protocol Handler . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345 20.6.1 Protocol Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346 20.6.2 Rx and Tx Shift Registers . . . . . . . . . . . . . . . . . . . . . . . . .347 20.6.3 Rx and Tx Shadow Registers . . . . . . . . . . . . . . . . . . . . . .347 20.6.4 Digital Loopback Multiplexer . . . . . . . . . . . . . . . . . . . . . . .347
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 321
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.6.5 State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348 20.6.5.1 4X Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348 20.6.5.2 Receiving a Message in Block Mode . . . . . . . . . . . . . . .348 20.6.5.3 Transmitting a Message in Block Mode . . . . . . . . . . . . .348 20.6.5.4 J1850 Bus Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349 20.6.5.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351 20.7 BDLC CPU Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352 20.7.1 BDLC Analog and Roundtrip Delay Register . . . . . . . . . .353 20.7.2 BDLC Control Register 1. . . . . . . . . . . . . . . . . . . . . . . . . .354 20.7.3 BDLC Control Register 2. . . . . . . . . . . . . . . . . . . . . . . . . .357 20.7.4 BDLC State Vector Register . . . . . . . . . . . . . . . . . . . . . . .364 20.7.5 BDLC Data Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366 20.8 Low-Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368 20.8.1 Wait Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368 20.8.2 Stop Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
NON-DISCLOSURE
Advance Information 322 Byte Data Link Controller-Digital (BDLC-D)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) Introduction
20.2 Introduction
The byte data link controller (BDLC) provides access to an external serial communication multiplex bus, operating according to the Society of Automotive Engineers (SAE) J1850 protocol.
20.3 Features
Features of the BDLC module include: * SAE J1850 class B data communications network interface compatible and ISO compatible for low speed (<125 kbps) serial data communications in automotive applications 10.4 kbps variable pulse width (VPW) bit format Digital noise filter Collision detection Hardware cyclical redundancy check (CRC) generation and checking Two power-saving modes with automatic wakeup on network activity Polling and CPU interrupts available Block mode receive and transmit supported Supports 4X receive mode, 41.6 kbps Digital loopback mode Analog loopback mode In-frame response (IFR) types 0, 1, 2, and 3 supported
* * * * * * * * * * *
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 323
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED 20.4 Functional Description
Figure 20-1 shows the organization of the BDLC module. The CPU interface contains the software addressable registers and provides the link between the CPU and the buffers. The buffers provide storage for data received and data to be transmitted onto the J1850 bus. The protocol handler is responsible for the encoding and decoding of data bits and special message symbols during transmission and reception. The MUX interface provides the link between the BDLC digital section and the analog physical interface. The wave shaping, driving, and digitizing of data is performed by the physical interface. Use of the BDLC module in message networking fully implements the SAE Standard J1850 Class B Data Communication Network Interface specification.
AGREEMENT
NOTE:
It is recommended that the reader be familiar with the SAE J1850 document and ISO Serial Communication document prior to proceeding with this section of the MC68HC08AS32 specification.
TO CPU
NON-DISCLOSURE
CPU INTERFACE
PROTOCOL HANDLER
MUX INTERFACE
PHYSICAL INTERFACE BDLC TO J1850 BUS
Figure 20-1. BDLC Block Diagram .
Advance Information 324 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) Functional Description
Table 20-1. BDLC I/O Register Summary
Addr. $003B Name BDLC Analog and Rou5ndtrip Read: Delay Register (BARD) Write: BDLC Control Register 1 Read: (BCR1) Write: Bit 7 ATE 6 RXPOL R R 0 IMSG CLKS R1 R0 R R 0 IE WCM 5 0 4 0 BO3 BO2 BO1 BO0 3 2 1 Bit 0
$003C
$003E
BDLC State Vector Register Read: (BSVR) Write: Read:
0 R
0 R
I3 R
I2 R
I1 R
I0 R
0 R
0 R
$003F
BDLC Data Register (BDR) Write:
BD7
BD6
BD5
BD4
BD3
BD2
BD1
BD0
R
= Reserved
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 325
NON-DISCLOSURE
AGREEMENT
$003D
BDLC Control Register 2 Read: ALOOP (BCR2) Write:
DLOOP
RX4XE
NBFS
TEOD
TSIFR
TMIFR1
TMIFR0
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.4.1 BDLC Operating Modes The BDLC has five main modes of operation which interact with the power supplies, pins, and the remainder of the MCU as shown in Figure 20-2.
POWER OFF
AGREEMENT
VDD VDD (MINIMUM)
VDD > VDD (MINIMUM) AND ANY MCU RESET SOURCE ASSERTED
RESET
ANY MCU RESET SOURCE ASSERTED (FROM ANY MODE) COP, ILLADDR, PU, RESET, LVR, POR
NO MCU RESET SOURCE ASSERTED
NETWORK ACTIVITY OR OTHER MCU WAKEUP
RUN
NETWORK ACTIVITY OR OTHER MCU WAKEUP
NON-DISCLOSURE
BDLC STOP
STOP INSTRUCTION OR WAIT INSTRUCTION AND WCM = 1
BDLC WAIT
WAIT INSTRUCTION AND WCM = 0
Figure 20-2. BDLC Operating Modes State Diagram
Advance Information 326 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) Functional Description
20.4.1.1 Power Off Mode This mode is entered from reset mode whenever the BDLC supply voltage, VDD, drops below its minimum specified value for the BDLC to guarantee operation. The BDLC will be placed in reset mode by low-voltage reset (LVR) before being powered down. In this mode, the pin input and output specifications are not guaranteed. 20.4.1.2 Reset Mode This mode is entered from the power off mode whenever the BDLC supply voltage, VDD, rises above its minimum specified value (VDD -10%) and some MCU reset source is asserted. The internal MCU reset must be asserted while powering up the BDLC or an unknown state will be entered and correct operation cannot be guaranteed. Reset mode is also entered from any other mode as soon as one of the MCU's possible reset sources (such as LVR, POR, COP watchdog, and reset pin, etc.) is asserted. In reset mode, the internal BDLC voltage references are operative; VDD is supplied to the internal circuits which are held in their reset state; and the internal BDLC system clock is running. Registers will assume their reset condition. Outputs are held in their programmed reset state. Therefore, inputs and network activity are ignored. 20.4.1.3 Run Mode This mode is entered from the reset mode after all MCU reset sources are no longer asserted. Run mode is entered from the BDLC wait mode whenever activity is sensed on the J1850 bus. Run mode is entered from the BDLC stop mode whenever network activity is sensed, although messages will not be received properly until the clocks have stabilized and the CPU is in run mode also. In this mode, normal network operation takes place. The user should ensure that all BDLC transmissions have ceased before exiting this mode.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 327
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.4.1.4 BDLC Wait Mode This power-conserving mode is entered automatically from run mode whenever the CPU executes a WAIT instruction and if the WCM bit in the BCR1 register is cleared previously. In this mode, the BDLC internal clocks continue to run. The first passive-to-active transition of the bus generates a CPU interrupt request from the BDLC which wakes up the BDLC and the CPU. In addition, if the BDLC receives a valid EOF symbol while operating in wait mode, then the BDLC also will generate a CPU interrupt request which wakes up the BDLC and the CPU. See 20.8.1 Wait Mode. 20.4.1.5 BDLC Stop Mode This power-conserving mode is entered automatically from run mode whenever the CPU executes a STOP instruction or if the CPU executes a WAIT instruction and the WCM bit in the BCR1 register is set previously. In this mode, the BDLC internal clocks are stopped but the physical interface circuitry is placed in a low-power mode and awaits network activity. If network activity is sensed, then a CPU interrupt request will be generated, restarting the BDLC internal clocks. See 20.8.2 Stop Mode. 20.4.1.6 Digital Loopback Mode When a bus fault has been detected, the digital loopback mode is used to determine if the fault condition is caused by failure in the node's internal circuits or elsewhere in the network, including the node's analog physical interface. In this mode, the transmit digital output pin (BDTxD) and the receive digital input pin (BDRxD) of the digital interface are disconnected from the analog physical interface and tied together to allow the digital portion of the BDLC to transmit and receive its own messages without driving the J1850 bus.
NON-DISCLOSURE
AGREEMENT
Advance Information 328 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
20.4.1.7 Analog Loopback Mode Analog loopback is used to determine if a bus fault has been caused by a failure in the node's off-chip analog transceiver or elsewhere in the network. The BCLD analog loopback mode does not modify the digital transmit or receive functions of the BDLC. It does, however, ensure that once analog loopback mode is exited, the BDLC will wait for an idle bus condition before participation in network communication resumes. If the off-chip analog transceiver has a loopback mode, it usually causes the input to the output drive stage to be looped back into the receiver, allowing the node to receive messages it has transmitted without driving the J1850 bus. In this mode, the output to the J1850 bus is typically high impedance. This allows the communication path through the analog transceiver to be tested without interfering with network activity. Using the BDLC analog loopback mode in conjunction with the analog transceiver's loopback mode ensures that, once the off-chip analog transceiver has exited loopback mode, the BCLD will not begin communicating before a known condition exists on the J1850 bus.
20.5 BDLC MUX Interface
The MUX interface is responsible for bit encoding/decoding and digital noise filtering between the protocol handler and the physical interface.
TO CPU
CPU INTERFACE
PROTOCOL HANDLER
MUX INTERFACE
PHYSICAL INTERFACE BDLC TO J1850 BUS
Figure 20-3. BDLC Block Diagram
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 329
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.5.1 Rx Digital Filter The receiver section of the BDLC includes a digital low pass filter to remove narrow noise pulses from the incoming message. An outline of the digital filter is shown in Figure 20-4.
INPUT SYNC RX DATA FROM PHYSICAL INTERFACE (BDRxD) DATA LATCH
4-BIT UP/DOWN COUTER UP/DOWN OUT
FILTERED RX DATA OUT
D
Q
D
Q
AGREEMENT
MUX INTERFACE CLOCK
Figure 20-4. BDLC Rx Digital Filter Block Diagram 20.5.1.1 Operation The clock for the digital filter is provided by the MUX interface clock (see fBDLC parameter in Table 20-4). At each positive edge of the clock signal, the current state of the receiver physical interface (BDRxD) signal is sampled. The BDRxD signal state is used to determine whether the counter should increment or decrement at the next negative edge of the clock signal. The counter will increment if the input data sample is high but decrement if the input sample is low. Therefore, the counter will thus progress either up toward 15 if, on average, the BDRxD signal remains high or progress down toward 0 if, on average, the BDRxD signal remains low. When the counter eventually reaches the value 15, the digital filter decides that the condition of the BDRxD signal is at a stable logic level 1 and the data latch is set, causing the filtered Rx data signal to become a logic level 1. Furthermore, the counter is prevented from overflowing and can only be decremented from this state.
NON-DISCLOSURE
Advance Information 330
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
Alternatively, should the counter eventually reach the value 0, the digital filter decides that the condition of the BDRxD signal is at a stable logic level 0 and the data latch is reset, causing the filtered Rx data signal to become a logic level 0. Furthermore, the counter is prevented from underflowing and can only be incremented from this state. The data latch will retain its value until the counter next reaches the opposite end point, signifying a definite transition of the signal. 20.5.1.2 Performance The performance of the digital filter is best described in the time domain rather than the frequency domain. If the signal on the BDRxD signal transitions, then there will be a delay before that transition appears at the filtered Rx data output signal. This delay will be between 15 and 16 clock periods, depending on where the transition occurs with respect to the sampling points. This filter delay must be taken into account when performing message arbitration. For example, if the frequency of the MUX interface clock (fBDLC) is 1.0486 MHz, then the period (tBDLC) is 954 ns and the maximum filter delay in the absence of noise will be 15.259 s. The effect of random noise on the BDRxD signal depends on the characteristics of the noise itself. Narrow noise pulses on the BDRxD signal will be ignored completely if they are shorter than the filter delay. This provides a degree of low pass filtering. If noise occurs during a symbol transition, the detection of that transition can be delayed by an amount equal to the length of the noise burst. This is just a reflection of the uncertainty of where the transition is truly occurring within the noise. Noise pulses that are wider than the filter delay, but narrower than the shortest allowable symbol length, will be detected by the next stage of the BDLC's receiver as an invalid symbol. Noise pulses that are longer than the shortest allowable symbol length will be detected normally as an invalid symbol or as invalid data when the frame's CRC is checked.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D) Advance Information 331
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.5.2 J1850 Frame Format All messages transmitted on the J1850 bus are structured using the format shown in Figure 20-5. J1850 states that each message has a maximum length of 101 PWM bit times or 12 VPW bytes, excluding SOF, EOD, NB, and EOF, with each byte transmitted MSB first. All VPW symbol lengths in the following descriptions are typical values at a 10.4 kbps bit rate.
DATA IDLE SOF PRIORITY (DATA0) MESSAGE ID (DATA1) DATAN CRC OPTIONAL N B IFR EOF
AGREEMENT
E O D
I F S
IDLE
Figure 20-5. J1850 Bus Message Format (VPW) SOF -- Start-of-Frame Symbol All messages transmitted onto the J1850 bus must begin with a long-active 200-s period SOF symbol. This indicates the start of a new message transmission. The SOF symbol is not used in the CRC calculation. Data -- In-Message Data Bytes The data bytes contained in the message include the message priority/type, message ID byte (typically the physical address of the responder), and any actual data being transmitted to the receiving node. The message format used by the BDLC is similar to the 3-byte consolidated header message format outlined by the SAE J1850 document. See SAE J1850 -- Class B Data Communications Network Interface for more information about 1- and 3-byte headers. Messages transmitted by the BDLC onto the J1850 bus must contain at least one data byte and, therefore, can be as short as one data byte and one CRC byte. Each data byte in the message is eight bits in length and is transmitted MSB to LSB.
NON-DISCLOSURE
Advance Information 332
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
CRC -- Cyclical Redundancy Check Byte This byte is used by the receiver(s) of each message to determine if any errors have occurred during the transmission of the message. The BDLC calculates the CRC byte and appends it onto any messages transmitted onto the J1850 bus. It also performs CRC detection on any messages it receives from the J1850 bus. CRC generation uses the divisor polynomial X8 + X4 + X3 + X2 + 1. The remainder polynomial initially is set to all ones. Each byte in the message after the start of frame (SOF) symbol is processed serially through the CRC generation circuitry. The one's complement of the remainder then becomes the 8-bit CRC byte, which is appended to the message after the data bytes in MSB-to-LSB order. When receiving a message, the BDLC uses the same divisor polynomial. All data bytes, excluding the SOF and end of data symbols (EOD) but including the CRC byte, are used to check the CRC. If the message is error free, the remainder polynomial will equal X7 + X6 + X2 = $C4, regardless of the data contained in the message. If the calculated CRC does not equal $C4, the BDLC will recognize this as a CRC error and set the CRC error flag in the BSVR. EOD -- End-of-Data Symbol
IFR -- In-Frame Response Bytes The IFR section of the J1850 message format is optional. Users desiring further definition of in-frame response should review the SAE J1850 -- Class B Data Communications Network Interface specification. EOF -- End-of-Frame Symbol This symbol is a long 280-s passive period on the J1850 bus and is longer than an end-of-data (EOD) symbol, which signifies the end of a message. Since an EOF symbol is longer than a 200-s EOD
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 333
NON-DISCLOSURE
The EOD symbol is a long 200-s passive period on the J1850 bus used to signify to any recipients of a message that the transmission by the originator has completed. No flag is set upon reception of the EOD symbol.
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
symbol, if no response is transmitted after an EOD symbol, it becomes an EOF, and the message is assumed to be completed. The EOF flag is set upon receiving the EOF symbol. IFS -- Inter-Frame Separation Symbol The IFS symbol is a 20-s passive period on the J1850 bus which allows proper synchronization between nodes during continuous message transmission. The IFS symbol is transmitted by a node after the completion of the end-of-frame (EOF) period and, therefore, is seen as a 300-s passive period. When the last byte of a message has been transmitted onto the J1850 bus and the EOF symbol time has expired, all nodes then must wait for the IFS symbol time to expire before transmitting a start-of-frame (SOF) symbol, marking the beginning of another message. However, if the BDLC is waiting for the IFS period to expire before beginning a transmission and a rising edge is detected before the IFS time has expired, it will synchronize internally to that edge. If a write to the BDR register (for instance, to initiate transmission) occurred on or before 104 * tBDLC from the received rising edge, then the BDLC will transmit and arbitrate for the bus. If a CPU write to the BDR register occurred after 104 * tBDLC from the detection of the rising edge, then the BDLC will not transmit, but will wait for the next IFS period to expire before attempting to transmit the byte. A rising edge may occur during the IFS period because of varying clock tolerances and loading of the J1850 bus, causing different nodes to observe the completion of the IFS period at different times. To allow for individual clock tolerances, receivers must synchronize to any SOF occurring during an IFS period. BREAK -- Break The BDLC cannot transmit a BREAK symbol. If the BDLC is transmitting at the time a BREAK is detected, it treats the BREAK as if a transmission error had occurred and halts transmission. If the BDLC detects a BREAK symbol while receiving a message, it treats the BREAK as a reception error and sets the invalid symbol flag in the BSVR, also ignoring the frame it was receiving. If while
Advance Information 334 Byte Data Link Controller-Digital (BDLC-D) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
NON-DISCLOSURE
AGREEMENT
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
receiving a message in 4X mode, the BDLC detects a BREAK symbol, it treats the BREAK as a reception error, sets the invalid symbol flag, and exits 4X mode (for example, the RX4XE bit in BCR2 is cleared automatically). If bus control is required after the BREAK symbol is received and the IFS time has elapsed, the programmer must resend the transmission byte using highest priority.
NOTE:
The J1850 protocol BREAK symbol is not related to the HC08 break module (See Section 11. Break Module (Break).)
IDLE -- Idle Bus An idle condition exists on the bus during any passive period after expiration of the IFS period (for instance, 300 s). Any node sensing an idle bus condition can begin transmission immediately.
20.5.3 J1850 VPW Symbols Huntsinger's variable pulse width modulation (VPW) is an encoding technique in which each bit is defined by the time between successive transitions and by the level of the bus between transitions (for instance, active or passive). Active and passive bits are used alternately. This encoding technique is used to reduce the number of bus transitions for a given bit rate. Each logic 1 or logic 0 contains a single transition and can be at either the active or passive level and one of two lengths, either 64 s or 128 s (tNOM at 10.4 kbps baud rate), depending upon the encoding of the previous bit. The start-of-frame (SOF), end-of-data (EOD), end-of-frame (EOF), and inter-frame separation (IFS) symbols always will be encoded at an assigned level and length. See Figure 20-6. Each message will begin with an SOF symbol an active symbol and, therefore, each data byte (including the CRC byte) will begin with a passive bit, regardless of whether it is a logic 1 or a logic 0. All VPW bit lengths stated in the following descriptions are typical values at a 10.4 kbps bit rate.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 335
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Logic 0 A logic 0 is defined as either: - An active-to-passive transition followed by a passive period 64 s in length, or - A passive-to-active transition followed by an active period 128 s in length See Figure 20-6(a).
AGREEMENT
ACTIVE 128 s PASSIVE OR 64 s
(A) LOGIC 0
ACTIVE 128 s PASSIVE (B) LOGIC 1 OR 64 s
NON-DISCLOSURE
ACTIVE 240 s PASSIVE (C) BREAK (D) START OF FRAME (E) END OF DATA 200 s 200 s
300 s ACTIVE 280 s PASSIVE (F) END OF FRAME (G) INTER-FRAME SEPARATION (H) IDLE 20 s IDLE > 300 s
Figure 20-6. J1850 VPW Symbols with Nominal Symbol Times
Advance Information 336 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
Logic 1 A logic 1 is defined as either: - An active-to-passive transition followed by a passive period 128 s in length, or - A passive-to-active transition followed by an active period 64 s in length See Figure 20-6(b). Normalization Bit (NB) The NB symbol has the same property as a logic 1 or a logic 0. It is only used in IFR message responses. Break Signal (BREAK) The BREAK signal is defined as a passive-to-active transition followed by an active period of at least 240 s (see Figure 20-6(c)). Start-of-Frame Symbol (SOF) The SOF symbol is defined as passive-to-active transition followed by an active period 200 s in length (see Figure 20-6(d)). This allows the data bytes which follow the SOF symbol to begin with a passive bit, regardless of whether it is a logic 1 or a logic 0. End-of-Data Symbol (EOD) The EOD symbol is defined as an active-to-passive transition followed by a passive period 200 s in length (see Figure 20-6(e)). End-of-Frame Symbol (EOF) The EOF symbol is defined as an active-to-passive transition followed by a passive period 280 s in length (see Figure 20-6(f)). If no IFR byte is transmitted after an EOD symbol is transmitted, after another 80 s the EOD becomes an EOF, indicating completion of the message. Inter-Frame Separation Symbol (IFS) The IFS symbol is defined as a passive period 300 s in length. The 20-s IFS symbol contains no transition, since when used it always appends to an EOF symbol (see Figure 20-6(g)).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 337
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Idle An idle is defined as a passive period greater than 300 s in length.
20.5.4 J1850 VPW Valid/Invalid Bits and Symbols The timing tolerances for receiving data bits and symbols from the J1850 bus have been defined to allow for variations in oscillator frequencies. In many cases the maximum time allowed to define a data bit or symbol is equal to the minimum time allowed to define another data bit or symbol. Since the minimum resolution of the BDLC for determining what symbol is being received is equal to a single period of the MUX interface clock (tBDLC), an apparent separation in these maximum time/minimum time concurrences equal to one cycle of tBDLC occurs. This one clock resolution allows the BDLC to differentiate properly between the different bits and symbols. This is done without reducing the valid window for receiving bits and symbols from transmitters onto the J1850 bus which have varying oscillator frequencies. In Huntsinger's' variable pulse width (VPW) modulation bit encoding, the tolerances for both the passive and active data bits received and the symbols received are defined with no gaps between definitions. For example, the maximum length of a passive logic 0 is equal to the minimum length of a passive logic 1, and the maximum length of an active logic 0 is equal to the minimum length of a valid SOF symbol. Invalid Passive Bit See Figure 20-7(1). If the passive-to-active received transition beginning the next data bit or symbol occurs between the active-to-passive transition beginning the current data bit (or symbol) and a, the current bit would be invalid.
NON-DISCLOSURE
Advance Information 338
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
200 s 128 s 64 s ACTIVE PASSIVE a ACTIVE PASSIVE a ACTIVE PASSIVE b ACTIVE PASSIVE c d c (4) VALID EOD SYMBOL b (3) VALID PASSIVE LOGIC 1 (2) VALID PASSIVE LOGIC 0
(1) INVALID PASSIVE BIT
Figure 20-7. J1850 VPW Received Passive Symbol Times Valid Passive Logic 0 See Figure 20-7(2). If the passive-to-active received transition beginning the next data bit (or symbol) occurs between a and b, the current bit would be considered a logic 0. Valid Passive Logic 1 See Figure 20-7(3). If the passive-to-active received transition beginning the next data bit (or symbol) occurs between b and c, the current bit would be considered a logic 1. Valid EOD Symbol See Figure 20-7(4). If the passive-to-active received transition beginning the next data bit (or symbol) occurs between c and d, the current symbol would be considered a valid end-of-data symbol (EOD).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 339
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
300 s 280 s
ACTIVE PASSIVE a ACTIVE b
(1) VALID EOF SYMBOL
(2) VALID EOF+ IFS SYMBOL c d
AGREEMENT
PASSIVE
Figure 20-8. J1850 VPW Received Passive EOF and IFS Symbol Times Valid EOF and IFS Symbol In Figure 20-8(1), if the passive-to-active received transition beginning the SOF symbol of the next message occurs between a and b, the current symbol will be considered a valid end-of-frame (EOF) symbol. See Figure 20-8(2). If the passive-to-active received transition beginning the SOF symbol of the next message occurs between c and d, the current symbol will be considered a valid EOF symbol followed by a valid inter-frame separation symbol (IFS). All nodes must wait until a valid IFS symbol time has expired before beginning transmission. However, due to variations in clock frequencies and bus loading, some nodes may recognize a valid IFS symbol before others and immediately begin transmitting. Therefore, any time a node waiting to transmit detects a passive-to-active transition once a valid EOF has been detected, it should immediately begin transmission, initiating the arbitration process. Idle Bus In Figure 20-8(2), if the passive-to-active received transition beginning the start-of-frame (SOF) symbol of the next message does not occur before d, the bus is considered to be idle, and any node wishing to transmit a message may do so immediately.
NON-DISCLOSURE
Advance Information 340
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
200 s 128 s 64 s ACTIVE (1) INVALID ACTIVE BIT PASSIVE a ACTIVE (2) VALID ACTIVE LOGIC 1 PASSIVE a ACTIVE (3) VALID ACTIVE LOGIC 0 PASSIVE b ACTIVE (4) VALID SOF SYMBOL PASSIVE c d c b
Figure 20-9. J1850 VPW Received Active Symbol Times Invalid Active Bit In Figure 20-9(1), if the active-to-passive received transition beginning the next data bit (or symbol) occurs between the passive-to-active transition beginning the current data bit (or symbol) and a, the current bit would be invalid. Valid Active Logic 1 In Figure 20-9(2), if the active-to-passive received transition beginning the next data bit (or symbol) occurs between a and b, the current bit would be considered a logic 1. Valid Active Logic 0 In Figure 20-9(3), if the active-to-passive received transition beginning the next data bit (or symbol) occurs between b and c, the current bit would be considered a logic 0.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 341
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Valid SOF Symbol In Figure 20-9(4), if the active-to-passive received transition beginning the next data bit (or symbol) occurs between c and d, the current symbol would be considered a valid SOF symbol. Valid BREAK Symbol In Figure 20-10, if the next active-to-passive received transition does not occur until after e, the current symbol will be considered a valid BREAK symbol. A BREAK symbol should be followed by a start-of-frame (SOF) symbol beginning the next message to be transmitted onto the J1850 bus. See 20.5.2 J1850 Frame Format for BDLC response to BREAK symbols.
AGREEMENT
240 s
ACTIVE (2) VALID BREAK SYMBOL PASSIVE e
NON-DISCLOSURE
Figure 20-10. J1850 VPW Received BREAK Symbol Times
Advance Information 342 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC MUX Interface
20.5.5 Message Arbitration Message arbitration on the J1850 bus is accomplished in a non-destructive manner, allowing the message with the highest priority to be transmitted, while any transmitters which lose arbitration simply stop transmitting and wait for an idle bus to begin transmitting again. If the BDLC wants to transmit onto the J1850 bus, but detects that another message is in progress, it waits until the bus is idle. However, if multiple nodes begin to transmit in the same synchronization window, message arbitration will occur beginning with the first bit after the SOF symbol and will continue with each bit thereafter. The variable pulse width modulation (VPW) symbols and J1850 bus electrical characteristics are chosen carefully so that a logic 0 (active or passive type) will always dominate over a logic 1 (active or passive type) that is simultaneously transmitted. Hence, logic 0s are said to be dominant and logic 1s are said to be recessive. Whenever a node detects a dominant bit on BDRxD when it transmitted a recessive bit, the node loses arbitration and immediately stops transmitting. This is known as bitwise arbitration.
0 ACTIVE TRANSMITTER A PASSIVE 0 ACTIVE TRANSMITTER B PASSIVE 0 ACTIVE J1850 BUS PASSIVE SOF DATA BIT 1
1
1
1
TRANSMITTER A DETECTS AN ACTIVE STATE ON THE BUS AND STOPS TRANSMITTING
1
1
0
0
1
1
0
0
TRANSMITTER B WINS ARBITRATION AND CONTINUES TRANSMITTING
DATA BIT 2
DATA BIT 3
DATA BIT 4
DATA BIT 5
Figure 20-11. J1850 VPW Bitwise Arbitrations
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 343
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Since a logic 0 dominates a logic 1, the message with the lowest value will have the highest priority and will always win arbitration. For instance, a message with priority 000 will win arbitration over a message with priority 011. This method of arbitration will work no matter how many bits of priority encoding are contained in the message. During arbitration, or even throughout the transmitting message, when an opposite bit is detected, transmission is stopped immediately unless it occurs on the 8th bit of a byte. In this case, the BDLC automatically will append up to two extra logic 1 bits and then stop transmitting. These two extra bits will be arbitrated normally and thus will not interfere with another message. The second logic 1 bit will not be sent if the first loses arbitration. If the BDLC has lost arbitration to another valid message, then the two extra logic 1s will not corrupt the current message. However, if the BDLC has lost arbitration due to noise on the bus, then the two extra logic 1s will ensure that the current message will be detected and ignored as a noise-corrupted message.
NON-DISCLOSURE
Advance Information 344 Byte Data Link Controller-Digital (BDLC-D)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC Protocol Handler
20.6 BDLC Protocol Handler
The protocol handler is responsible for framing, arbitration, CRC generation/checking, and error detection. The protocol handler conforms to SAE J1850 -- Class B Data Communications Network Interface.
NOTE:
Motorola assumes that the reader is familiar with the J1850 specification before this protocol handler description is read.
TO CPU
CPU INTERFACE
PROTOCOL HANDLER
MUX INTERFACE
PHYSICAL INTERFACE BDLC TO J1850 BUS
Figure 20-12. BDLC Block Diagram
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 345
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.6.1 Protocol Architecture The protocol handler contains the state machine, Rx shadow register, Tx shadow register, Rx shift register, Tx shift register, and loopback multiplexer as shown in Figure 20-13.
TO PHYSICAL INTERFACE BDRxD BDTxD
AGREEMENT
CONTROL
DLOOP FROM BCR2 LOOPBACK CONTROL
LOOPBACK MULTIPLEXER RxD BDTxD ALOOP Tx DATA 8
STATE MACHINE
Rx SHIFT REGISTER
Tx SHIFT REGISTER
Rx SHADOW REGISTER
Tx SHADOW REGISTER
NON-DISCLOSURE
Rx DATA
TO CPU INTERFACE AND Rx/Tx BUFFERS
Figure 20-13. BDLC Protocol Handler Outline
Advance Information 346 Byte Data Link Controller-Digital (BDLC-D)
CONTROL
8
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC Protocol Handler
20.6.2 Rx and Tx Shift Registers The Rx shift register gathers received serial data bits from the J1850 bus and makes them available in parallel form to the Rx shadow register. The Tx shift register takes data, in parallel form, from the Tx shadow register and presents it serially to the state machine so that it can be transmitted onto the J1850 bus.
20.6.3 Rx and Tx Shadow Registers Immediately after the Rx shift register has completed shifting in a byte of data, this data is transferred to the Rx shadow register and RDRF or RXIFR is set (see 20.7.4 BDLC State Vector Register) and an interrupt is generated if the interrupt enable bit (IE) in BCR1 is set. After the transfer takes place, this new data byte in the Rx shadow register is available to the CPU interface, and the Rx shift register is ready to shift in the next byte of data. Data in the Rx shadow register must be retrieved by the CPU before it is overwritten by new data from the Rx shift register. Once the Tx shift register has completed its shifting operation for the current byte, the data byte in the Tx shadow register is loaded into the Tx shift register. After this transfer takes place, the Tx shadow register is ready to accept new data from the CPU when TDRE flag in BSVR is set.
20.6.4 Digital Loopback Multiplexer The digital loopback multiplexer connects RxD to either BDTxD or BDRxD, depending on the state of the DLOOP bit in the BCR2 register (See 20.7.3 BDLC Control Register 2).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 347
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
20.6.5 State Machine All of the functions associated with performing the protocol are executed or controlled by the state machine. The state machine is responsible for framing, collision detection, arbitration, CRC generation/checking, and error detection. The following sections describe the BDLC's actions in a variety of situations. 20.6.5.1 4X Mode
AGREEMENT
The BDLC can exist on the same J1850 bus as modules which use a special 4X (41.6 kbps) mode of J1850 variable pulse width modulation (VPW) operation. The BDLC cannot transmit in 4X mode, but can receive messages in 4X mode, if the RX4X bit is set in BCR2 register. If the RX4X bit is not set in the BCR2 register, any 4X message on the J1850 bus is treated as noise by the BDLC and is ignored. 20.6.5.2 Receiving a Message in Block Mode Although not a part of the SAE J1850 protocol, the BDLC does allow for a special block mode of operation of the receiver. As far as the BDLC is concerned, a block mode message is simply a long J1850 frame that contains an indefinite number of data bytes. All of the other features of the frame remain the same, including the SOF, CRC, and EOD symbols. Another node wishing to send a block mode transmission must first inform all other nodes on the network that this is about to happen. This is usually accomplished by sending a special predefined message. 20.6.5.3 Transmitting a Message in Block Mode A block mode message is transmitted inherently by simply loading the bytes one by one into the BDR register until the message is complete. The programmer should wait until the TDRE flag (see 20.7.4 BDLC State Vector Register) is set prior to writing a new byte of data into the BDR register. The BDLC does not contain any predefined maximum J1850 message length requirement.
NON-DISCLOSURE
Advance Information 348 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC Protocol Handler
20.6.5.4 J1850 Bus Errors The BDLC detects several types of transmit and receive errors which can occur during the transmission of a message onto the J1850 bus. Transmission Error If the message transmitted by the BDLC contains invalid bits or framing symbols on non-byte boundaries, this constitutes a transmission error. When a transmission error is detected, the BDLC immediately will cease transmitting. The error condition ($1C) is reflected in the BSVR register (see Table 20-6). If the interrupt enable bit (IE in BCR1) is set, a CPU interrupt request from the BDLC is generated. CRC Error A cyclical redundancy check (CRC) error is detected when the data bytes and CRC byte of a received message are processed and the CRC calculation result is not equal to $C4. The CRC code will detect any single and 2-bit errors, as well as all 8-bit burst errors and almost all other types of errors. The CRC error flag ($18 in BSVR) is set when a CRC error is detected. (See 20.7.4 BDLC State Vector Register.) Symbol Error A symbol error is detected when an abnormal (invalid) symbol is detected in a message being received from the J1850 bus. However, if the BDLC is transmitting when this happens, it will be treated as a loss of arbitration ($14 in BSVR) rather than a transmitter error. The ($1C) symbol invalid or the out-of-range flag is set when a symbol error is detected. Therefore, ($1C) symbol invalid flag is stacked behind the ($14) LOA flag during a transmission error process. (See 20.7.4 BDLC State Vector Register.) Framing Error A framing error is detected if an EOD or EOF symbol is detected on a non-byte boundary from the J1850 bus. A framing error also is detected if the BDLC is transmitting the EOD and instead receives an active symbol. The ($1C) symbol invalid or the out-of-range flag is set when a framing error is detected. (See 20.7.4 BDLC State Vector Register.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D) Advance Information 349
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Bus Fault If a bus fault occurs, the response of the BDLC will depend upon the type of bus fault. If the bus is shorted to battery, the BDLC will wait for the bus to fall to a passive state before it will attempt to transmit a message. As long as the short remains, the BDLC will never attempt to transmit a message onto the J1850 bus. If the bus is shorted to ground, the BDLC will see an idle bus, begin to transmit the message, and then detect a transmission error ($1C in BSVR), since the short to ground would not allow the bus to be driven to the active (dominant) SOF state. The BDLC will abort that transmission and wait for the next CPU command to transmit. In any case, if the bus fault is temporary, as soon as the fault is cleared, the BDLC will resume normal operation. If the bus fault is permanent, it may result in permanent loss of communication on the J1850 bus. (See 20.7.4 BDLC State Vector Register.) BREAK -- Break If a BREAK symbol is received while the BDLC is transmitting or receiving, an invalid symbol ($1C in BSVR) interrupt will be generated. Reading the BSVR register (see 20.7.4 BDLC State Vector Register) will clear this interrupt condition. The BDLC will wait for the bus to idle, then wait for a start-of-frame (SOF) symbol. The BDLC cannot transmit a BREAK symbol. It can only receive a BREAK symbol from the J1850 bus.
NON-DISCLOSURE
Advance Information 350
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC Protocol Handler
20.6.5.5 Summary Table 20-2. BDLC J1850 Bus Error Summary
Error Condition BDLC Function For invalid bits or framing symbols on non-byte boundaries, invalid symbol interrupt will be generated. BDLC stops transmission. CRC error interrupt will be generated. The BDLC will wait for SOF. The BDLC will abort transmission immediately. Invalid symbol interrupt will be generated. Invalid symbol interrupt will be generated. The BDLC will wait for start-of-frame (SOF). The BDLC will not transmit until the bus is idle. Thermal overload will shut down physical interface. Fault condition is reflected in BSVR as an invalid symbol. The BDLC will wait for the next valid SOF. Invalid symbol interrupt will be generated.
Transmission Error
Cyclical Redundancy Check (CRC) Error Invalid Symbol: BDLC Receives Invalid Bits (Noise)
Framing Error
Bus Short to VDD
Bus Short to GND
BDLC Receives BREAK Symbol.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 351
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED 20.7 BDLC CPU Interface
The CPU interface provides the interface between the CPU and the BDLC and consists of five user registers. * * * * BDLC analog and roundtrip delay register (BARD) BDLC control register 1 (BCR1) BDLC control register 2 (BCR2) BDLC state vector register (BSVR) BDLC data register (BDR)
AGREEMENT
*
TO CPU
CPU INTERFACE
PROTOCOL HANDLER
MUX INTERFACE
NON-DISCLOSURE
PHYSICAL INTERFACE BDLC TO J1850 BUS
Figure 20-14. BDLC Block Diagram
Advance Information 352 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
20.7.1 BDLC Analog and Roundtrip Delay Register This register programs the BDLC to compensate for various delays of different external transceivers. The default delay value is16 s. Timing adjustments from 9 s to 24 s in steps of 1 s are available. The BARD register can be written only once after each reset, after which they become read-only bits. The register may be read at any time.
Address: $003B Bit 7 Read: ATE Write: Reset: 1 R 1 = Reserved RXPOL R 0 R 0 0 1 1 1 6 5 0 4 0 BO3 BO2 BO1 BO0 3 2 1 Bit 0
Figure 20-15. BDLC Analog and Roundtrip Delay Register (BARD) ATE -- Analog Transceiver Enable Bit The analog transceiver enable (ATE) bit is used to select either the on-board or an off-chip analog transceiver. 1 = Select on-board analog transceiver 0 = Select off-chip analog transceiver
NOTE:
This device does not contain an on-board transceiver. This bit should be programmed to a logic 0 for proper operation.
RXPOL -- Receive Pin Polarity Bit The receive pin polarity (RXPOL) bit is used to select the polarity of an incoming signal on the receive pin. Some external analog transceivers invert the receive signal from the J1850 bus before feeding it back to the digital receive pin. 1 = Select normal/true polarity; true non-inverted signal from the J1850 bus; for example, the external transceiver does not invert the receive signal 0 = Select inverted polarity, where an external transceiver inverts the receive signal from the J1850 bus B03-B00 -- BARD Offset Bits
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 353
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Table 20-3 shows the expected transceiver delay with respect to BARD offset values. Table 20-3. BDLC Transceiver Delay
BARD Offset Bits B0[3:0] 0000 0001 0010 Corresponding Expected Transceiver's Delays (s) 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
AGREEMENT
0011 0100 0101 0110 0111 1000 1001 1010 1011 1100 1101
NON-DISCLOSURE
1110 1111
20.7.2 BDLC Control Register 1 This register is used to configure and control the BDLC.
Address: $003C Bit 7 Read: IMSG Write: Reset: 1 R 1 = Reserved 1 0 CLKS R1 R0 R 0 R 0 0 0 6 5 4 3 0 2 0 IE WCM 1 Bit 0
Figure 20-16. BDLC Control Register 1 (BCR1)
Advance Information 354 Byte Data Link Controller-Digital (BDLC-D) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
IMSG -- Ignore Message Bit This bit is used to disable the receiver until a new start-of-frame (SOF) is detected. 1 = Disable receiver. When set, all BDLC interrupt requests will be masked and the status bits will be held in their reset state. If this bit is set while the BDLC is receiving a message, the rest of the incoming message will be ignored. 0 = Enable receiver. This bit is cleared automatically by the reception of an SOF symbol or a BREAK symbol. It will then generate interrupt requests and will allow changes of the status register to occur. However, these interrupts may still be masked by the interrupt enable (IE) bit. CLKS -- Clock Bit The nominal BDLC operating frequency (fBDLC) must always be 1.048576 MHz or 1 MHz for J1850 bus communications to take place. The CLKS register bit allows the user to select the frequency (1.048576 MHz or 1 MHz) used to adjust symbol timing automatically. 1 = Binary frequency (1.048576 MHz) selected for fBDLC 0 = Integer frequency (1 MHz) selected for fBDLC R1 and R0 -- Rate Select Bits These bits determine the amount by which the frequency of the MCU CGMXCLK signal is divided to form the MUX interface clock (fBDLC) which defines the basic timing resolution of the MUX interface. They may be written only once after reset, after which they become read-only bits. The nominal frequency of fBDLC must always be 1.048576 MHz or 1.0 MHz for J1850 bus communications to take place. Hence, the value programmed into these bits is dependent on the chosen MCU system clock frequency per Table 20-4.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 355
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
Table 20-4. BDLC Rate Selection
fXCLK Frequency 1.049 MHz 2.097 MHz 4.194 MHz 8.389 MHz 1.000 MHz 2.000 MHz R1 0 0 1 1 0 0 1 1 R0 0 1 0 1 0 1 0 1 Division 1 2 4 8 1 2 4 8 fBDLC 1.049 MHz 1.049 MHz 1.049 MHz 1.049 MHz 1.00 MHz 1.00 MHz 1.00 MHz 1.00 MHz
AGREEMENT
4.000 MHz 8.000 MHz
IE-- Interrupt Enable Bit This bit determines whether the BDLC will generate CPU interrupt requests in run mode. It does not affect CPU interrupt requests when exiting the BDLC stop or BDLC wait modes. Interrupt requests will be maintained until all of the interrupt request sources are cleared by performing the specified actions upon the BDLC's registers. Interrupts that were pending at the time that this bit is cleared may be lost. 1 = Enable interrupt requests from BDLC 0 = Disable interrupt requests from BDLC If the programmer does not wish to use the interrupt capability of the BDLC, the BDLC state vector register (BSVR) can be polled periodically by the programmer to determine BDLC states. See 20.7.4 BDLC State Vector Register for a description of the BSVR. WCM -- Wait Clock Mode Bit This bit determines the operation of the BDLC during CPU wait mode. See 20.8.2 Stop Mode and 20.8.1 Wait Mode for more details on its use. 1 = Stop BDLC internal clocks during CPU wait mode 0 = Run BDLC internal clocks during CPU wait mode
NON-DISCLOSURE
Advance Information 356
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
20.7.3 BDLC Control Register 2 This register controls transmitter operations of the BDLC. It is recommended that BSET and BCLR instructions be used to manipulate data in this register to ensure that the register's content does not change inadvertently.
Address: $003D Bit 7 Read: ALOOP Write: Reset: 1 1 0 0 0 0 0 0 DLOOP RX4XE NBFS TEOD TSIFR TMIFR1 TMIFR0 6 5 4 3 2 1 Bit 0
Figure 20-17. BDLC Control Register 2 (BCR2) ALOOP -- Analog Loopback Mode Bit This bit determines whether the J1850 bus will be driven by the analog physical interface's final drive stage. The programmer can use this bit to reset the BDLC state machine to a known state after the off-chip analog transceiver is placed in loopback mode. When the user clears ALOOP, to indicate that the off-chip analog transceiver is no longer in loopback mode, the BDLC waits for an EOF symbol before attempting to transmit. 1 = Input to the analog physical interface's final drive stage is looped back to the BDLC receiver. The J1850 bus is not driven. 0 = The J1850 bus will be driven by the BDLC. After the bit is cleared, the BDLC requires the bus to be idle for a minimum of end-of-frame symbol time (tTRV4) before message reception or a minimum of inter-frame symbol time (tTRV6) before message transmission. (See 21.16 BDLC Receiver VPW Symbol Timings.)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 357
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
DLOOP -- Digital Loopback Mode Bit This bit determines the source to which the digital receive input (BDRxD) is connected and can be used to isolate bus fault conditions (see Figure 20-13). If a fault condition has been detected on the bus, this control bit allows the programmer to connect the digital transmit output to the digital receive input. In this configuration, data sent from the transmit buffer will be reflected back into the receive buffer. If no faults exist in the BDLC, the fault is in the physical interface block or elsewhere on the J1850 bus. 1 = When set, BDRxD is connected to BDTxD. The BDLC is now in digital loopback mode. 0 = When cleared, BDTxD is not connected to BDRxD. The BDLC is taken out of digital loopback mode and can now drive the J1850 bus normally. RX4XE -- Receive 4X Enable Bit This bit determines if the BDLC operates at normal transmit and receive speed (10.4 kbps) or receive only at 41.6 kbps. This feature is useful for fast download of data into a J1850 node for diagnostic or factory programming of the node. 1 = When set, the BDLC is put in 4X receive-only operation. 0 = When cleared, the BDLC transmits and receives at 10.4 kbps. NBFS -- Normalization Bit Format Select Bit This bit controls the format of the normalization bit (NB). (See Figure 20-18.) SAE J1850 strongly encourages using an active long (logic 0) for in-frame responses containing cyclical redundancy check (CRC) and an active short (logic 1) for in-frame responses without CRC. 1 = NB that is received or transmitted is a 0 when the response part of an in-frame response (IFR) ends with a CRC byte. NB that is received or transmitted is a 1 when the response part of an in-frame response (IFR) does not end with a CRC byte. 0 = NB that is received or transmitted is a 1 when the response part of an in-frame response (IFR) ends with a CRC byte. NB that is received or transmitted is a 0 when the response part of an in-frame response (IFR) does not end with a CRC byte.
NON-DISCLOSURE
Advance Information 358
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 Byte Data Link Controller-Digital (BDLC-D) MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
TEOD -- Transmit End of Data Bit This bit is set by the programmer to indicate the end of a message is being sent by the BDLC. It will append an 8-bit CRC after completing transmission of the current byte. This bit also is used to end an in-frame response (IFR). If the transmit shadow register is full when TEOD is set, the CRC byte will be transmitted after the current byte in the Tx shift register and the byte in the Tx shadow register have been transmitted. (See 20.6.3 Rx and Tx Shadow Registers for a description of the transmit shadow register.) Once TEOD is set, the transmit data register empty flag (TDRE) in the BDLC state vector register (BSVR) is cleared to allow lower priority interrupts to occur. (See 20.7.4 BDLC State Vector Register.) 1 = Transmit end-of-data (EOD) symbol 0 = The TEOD bit will be cleared automatically at the rising edge of the first CRC bit that is sent or if an error is detected. When TEOD is used to end an IFR transmission, TEOD is cleared when the BDLC receives back a valid EOD symbol or an error condition occurs. TSIFR, TMIFR1, and TMIFR0 -- Transmit In-Frame Response Control Bits These three bits control the type of in-frame response being sent. The programmer should not set more than one of these control bits to a 1 at any given time. However, if more than one of these three control bits are set to 1, the priority encoding logic will force these register bits to a known value as shown in Table 20-5. For example, if 011 is written to TSIFR, TMIFR1, and TMIFR0, then internally they will be encoded as 010. However, when these bits are read back, they will read 011. Table 20-5. BDLC Transmit In-Frame Response Control Bit Priority Encoding
Write/Read TSIFR 0 1 0 0 Write/Read TMIFR1 0 X 1 0 Write/Read TMIFR0 0 X X 1 Actual TSIFR 0 1 0 0 Actual TMIFR1 0 0 1 0 Actual TMIFR0 0 0 0 1
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 359
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
The BDLC supports the in-frame response (IFR) feature of J1850 by setting these bits correctly. The four types of J1850 IFR are shown below. The purpose of the in-frame response modes is to allow multiple nodes to acknowledge receipt of the data by responding with their personal ID or physical address in a concatenated manner after they have seen the EOD symbol. If transmission arbitration is lost by a node while sending its response, it continues to transmit its ID/address until observing its unique byte in the response stream. For VPW modulation, because the first bit of the IFR is always passive, a normalization bit (active) must be generated by the responder and sent prior to its ID/address byte. When there are multiple responders on the J1850 bus, only one normalization bit is sent which assists all other transmitting nodes to sync up their response.
AGREEMENT
EOF EOD
SOF SOF
HEADER
DATA FIELD
CRC
TYPE 0 -- NO IFR EOD EOF EOD HEADER DATA FIELD CRC NB ID
TYPE 1 -- SINGLE BYTE TRANSMITTED FROM A SINGLE RESPONDER
NON-DISCLOSURE
EOF EOD
EOD
NB = Normalization Bit ID = Identifier (usually the physical address of the responder(s))
Advance Information 360 Byte Data Link Controller-Digital (BDLC-D)
SOF SOF
HEADER
DATA FIELD
CRC
NB
ID1
ID N
TYPE 2 -- SINGLE BYTE TRANSMITTED FROM MULTIPLE RESPONDERS EOF EOD EOD
HEADER
DATA FIELD
CRC
NB
IFR DATA FIELD
CRC (OPTIONAL)
TYPE 3 -- MULTIPLE BYTES TRANSMITTED FROM A SINGLE RESPONDER
Figure 20-18. Types of In-Frame Response (IFR)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
TSIFR -- Transmit Single Byte IFR with No CRC (Type 1 or 2) Bit The TSIFR bit is used to request the BDLC to transmit the byte in the BDLC data register (BDR, $003F) as a single byte IFR with no CRC. Typically, the byte transmitted is a unique identifier or address of the transmitting (responding) node. See Figure 20-18. 1 = If this bit is set prior to a valid EOD being received with no CRC error, once the EOD symbol has been received the BDLC will attempt to transmit the appropriate normalization bit followed by the byte in the BDR. 0 = The TSIFR bit will be cleared automatically, once the BDLC has successfully transmitted the byte in the BDR onto the bus, or TEOD is set, or an error is detected on the bus. If the programmer attempts to set the TSIFR bit immediately after the EOD symbol has been received from the bus, the TSIFR bit will remain in the reset state and no attempt will be made to transmit the IFR byte. If a loss of arbitration occurs when the BDLC attempts to transmit and after the IFR byte winning arbitration completes transmission, the BDLC will again attempt to transmit the BDR (with no normalization bit). The BDLC will continue transmission attempts until an error is detected on the bus, or TEOD is set, or the BDLC transmission is successful. If loss or arbitration occurs in the last two bits of the IFR byte, two additional 1 bits will not be sent out because the BDLC will attempt to retransmit the byte in the transmit shift register after the IRF byte winning arbitration completes transmission. TMIFR1 -- Transmit Multiple Byte IFR with CRC (Type 3) Bit The TMIFR1 bit requests the BDLC to transmit the byte in the BDLC data register (BDR) as the first byte of a multiple byte IFR with CRC or as a single byte IFR with CRC. Response IFR bytes are still subject to J1850 message length maximums (see 20.5.2 J1850 Frame Format and Figure 20-18). If this bit is set prior to a valid EOD being received with no CRC error, once the EOD symbol has been received the BDLC will attempt to transmit the appropriate normalization bit followed by IFR bytes. The
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 361
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
programmer should set TEOD after the last IFR byte has been written into the BDR register. After TEOD has been set and the last IFR byte has been transmitted, the CRC byte is transmitted. 0 = The TMIFR1 bit will be cleared automatically - once the BDLC has successfully transmitted the CRC byte and EOD symbol - by the detection of an error on the multiplex bus or by a transmitter underrun caused when the programmer does not write another byte to the BDR after the TDRE interrupt. If the TMIFR1 bit is set, the BDLC will attempt to transmit the normalization symbol followed by the byte in the BDR. After the byte in the BDR has been loaded into the transmit shift register, a TDRE interrupt (see 20.7.4 BDLC State Vector Register) will occur similar to the main message transmit sequence. The programmer should then load the next byte of the IFR into the BDR for transmission. When the last byte of the IFR has been loaded into the BDR, the programmer should set the TEOD bit in the BDLC control register 2 (BCR2). This will instruct the BDLC to transmit a CRC byte once the byte in the BDR is transmitted and then transmit an EOD symbol, indicating the end of the IFR portion of the message frame. However, if the programmer wishes to transmit a single byte followed by a CRC byte, the programmer should load the byte into the BDR before the EOD symbol has been received, and then set the TMIFR1 bit. Once the TDRE interrupt occurs, the programmer should then set the TEOD bit in the BCR2. This will result in the byte in the BDR being the only byte transmitted before the IFR CRC byte, and no TDRE interrupt will be generated. If the programmer attempts to set the TMIFR1 bit immediately after the EOD symbol has been received from the bus, the TMIFR1 bit will remain in the reset state, and no attempt will be made to transmit an IFR byte. If a loss of arbitration occurs when the BDLC is transmitting any byte of a multiple byte IFR, the BDLC will go to the loss of arbitration state, set the appropriate flag, and cease transmission. If the BDLC loses arbitration during the IFR, the TMIFR1 bit will be cleared and no attempt will be made to retransmit the byte in the BDR. If loss of arbitration occurs in the last two bits of the IFR byte, two additional 1 bits will be sent out.
Advance Information 362 Byte Data Link Controller-Digital (BDLC-D) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
NON-DISCLOSURE
AGREEMENT
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
NOTE:
The extra logic 1s are an enhancement to the J1850 protocol which forces a byte boundary condition fault. This is helpful in preventing noise from going onto the J1850 bus from a corrupted message.
TMIFR0 -- Transmit Multiple Byte IFR without CRC (Type 3) Bit The TMIFR0 bit is used to request the BDLC to transmit the byte in the BDLC data register (BDR) as the first byte of a multiple byte IFR without CRC. Response IFR bytes are still subject to J1850 message length maximums (see 20.5.2 J1850 Frame Format and Figure 20-18). 1 = If this bit is set prior to a valid EOD being received with no CRC error, once the EOD symbol has been received the BDLC will attempt to transmit the appropriate normalization bit followed by IFR bytes. The programmer should set TEOD after the last IFR byte has been written into the BDR register. After TEOD has been set, the last IFR byte to be transmitted will be the last byte which was written into the BDR register. 0 = The TMIFR0 bit will be cleared automatically; once the BDLC has successfully transmitted the EOD symbol; by the detection of an error on the multiplex bus; or by a transmitter underrun caused when the programmer does not write another byte to the BDR after the TDRE interrupt. If the TMIFR0 bit is set, the BDLC will attempt to transmit the normalization symbol followed by the byte in the BDR. After the byte in the BDR has been loaded into the transmit shift register, a TDRE interrupt (see 20.7.4 BDLC State Vector Register) will occur similar to the main message transmit sequence. The programmer should then load the next byte of the IFR into the BDR for transmission. When the last byte of the IFR has been loaded into the BDR, the programmer should set the TEOD bit in the BCR2. This will instruct the BDLC to transmit an EOD symbol once the byte in the BDR is transmitted, indicating the end of the IFR portion of the message frame. The BDLC will not append a CRC when the TMIFR0 is set. If the programmer attempts to set the TMIFR0 bit after the EOD symbol has been received from the bus, the TMIFR0 bit will remain in the reset state, and no attempt will be made to transmit an IFR byte.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 363
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
If a loss of arbitration occurs when the BDLC is transmitting, the TMIFR0 bit will be cleared and no attempt will be made to retransmit the byte in the BDR. If loss of arbitration occurs in the last two bits of the IFR byte, two additional 1 bits (active short bits) will be sent out.
NOTE:
The extra logic 1s are an enhancement to the J1850 protocol which forces a byte boundary condition fault. This is helpful in preventing noise from going onto the J1850 bus from a corrupted message.
AGREEMENT
20.7.4 BDLC State Vector Register This register is provided to substantially decrease the CPU overhead associated with servicing interrupts while under operation of a multiplex protocol. It provides an index offset that is directly related to the BDLC's current state, which can be used with a user-supplied jump table to rapidly enter an interrupt service routine. This eliminates the need for the user to maintain a duplicate state machine in software.
Address: $003E Bit 7 Read: 0 R 0 R 6 0 R 0 = Reserved 5 I3 R 0 4 I2 R 0 3 I1 R 0 2 I0 R 0 1 0 R 0 Bit 0 0 R 0
NON-DISCLOSURE
Write: Reset:
Figure 20-19. BDLC State Vector Register (BSVR) I0, I1, I2, and I3 -- Interrupt Source Bits These bits indicate the source of the interrupt request that currently is pending. The encoding of these bits are listed in Table 20-6.
Advance Information 364 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
Table 20-6. BDLC Interrupt Sources
BSVR $00 $04 $08 $0C $10 $14 $18 $1C $20 I3 0 0 0 0 0 0 0 0 1 I2 0 0 0 0 1 1 1 1 0 I1 0 0 1 1 0 0 1 1 0 I0 0 1 0 1 0 1 0 1 0 Interrupt Source No Interrupts Pending Received EOF Received IFR Byte (RXIFR) BDLC Rx Data Register Full (RDRF) BDLC Tx Data Register Empty (TDRE) Loss of Arbitration Cyclical Redundancy Check (CRC) Error Symbol Invalid or Out of Range Wakeup Priority 0 (Lowest) 1 2 3 4 5 6 7 8 (Highest)
Bits I0, I1, I2, and I3 are cleared by a read of the BSVR except when the BDLC data register needs servicing (RDRF, RXIFR, or TDRE conditions). RXIFR and RDRF can be cleared only by a read of the BSVR followed by a read of the BDLC data register (BDR). TDRE can either be cleared by a read of the BSVR followed by a write to the BDLC BDR or by setting the TEOD bit in BCR2. Upon receiving a BDLC interrupt, the user can read the value within the BSVR, transferring it to the CPU's index register. The value can then be used to index into a jump table, with entries four bytes apart, to quickly enter the appropriate service routine. For example:
Service * * JMPTAB LDX JMP BSVR JMPTAB,X Fetch State Vector Number Enter service routine, (must end in RTI) Service condition #0 Service condition #1 Service condition #2
JMP NOP JMP NOP JMP NOP JMP END
SERVE0 SERVE1 SERVE2
* SERVE8 Service condition #8
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 365
NON-DISCLOSURE
AGREEMENT
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED
NOTE:
The NOPs are used only to align the JMPs onto 4-byte boundaries so that the value in the BSVR can be used intact. Each of the service routines must end with an RTI instruction to guarantee correct continued operation of the device. Note also that the first entry can be omitted since it corresponds to no interrupt occurring.
The service routines should clear all of the sources that are causing the pending interrupts. Note that the clearing of a high priority interrupt may still leave a lower priority interrupt pending, in which case bits I0, I1, and I2 of the BSVR will then reflect the source of the remaining interrupt request. If fewer states are used or if a different software approach is taken, the jump table can be made smaller or omitted altogether.
AGREEMENT
20.7.5 BDLC Data Register
Address: $003F Bit 7 Read: D7 D6 D5 D4 D3 D2 D1 D0 6 5 4 3 2 1 Bit 0
NON-DISCLOSURE
Write: Reset: Unaffected by Reset
Figure 20-20. BDLC Data Register (BDR) This register is used to pass the data to be transmitted to the J1850 bus from the CPU to the BDLC. It is also used to pass data received from the J1850 bus to the CPU. Each data byte (after the first one) should be written only after a Tx data register empty (TDRE) state is indicated in the BSVR. Data read from this register will be the last data byte received from the J1850 bus. This received data should only be read after an Rx data register full (RDRF) interrupt has occurred. (See 20.7.4 BDLC State Vector Register.)
Advance Information 366 Byte Data Link Controller-Digital (BDLC-D)
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) BDLC CPU Interface
To abort an in-progress transmission, the programmer should stop loading data into the BDR. This will cause a transmitter underrun error and the BDLC automatically will disable the transmitter on the next non-byte boundary. This means that the earliest a transmission can be halted is after at least one byte plus two extra logic 1s have been transmitted. The receiver will pick this up as an error and relay it in the state vector register as an invalid symbol error.
NOTE:
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 367
NON-DISCLOSURE
The extra logic 1s are an enhancement to the J1850 protocol which forces a byte boundary condition fault. This is helpful in preventing noise from going onto the J1850 bus from a corrupted message.
AGREEMENT
The BDR is double buffered via a transmit shadow register and a receive shadow register. After the byte in the transmit shift register has been transmitted, the byte currently stored in the transmit shadow register is loaded into the transmit shift register. Once the transmit shift register has shifted the first bit out, the TDRE flag is set, and the shadow register is ready to accept the next data byte. The receive shadow register works similarly. Once a complete byte has been received, the receive shift register stores the newly received byte into the receive shadow register. The RDRF flag is set to indicate that a new byte of data has been received. The programmer has one BDLC byte reception time to read the shadow register and clear the RDRF flag before the shadow register is overwritten by the newly received byte.
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED 20.8 Low-Power Modes
The following information concerns wait mode and stop mode.
20.8.1 Wait Mode This power-conserving mode is entered automatically from run mode whenever the CPU executes a WAIT instruction and the WCM bit in BDLC control register 1 (BCR1) is previously clear. In BDLC wait mode, the BDLC cannot drive any data. A subsequent successfully received message, including one that is in progress at the time that this mode is entered, will cause the BDLC to wake up and generate a CPU interrupt request if the interrupt enable (IE) bit in the BDLC control register 1 (BCR1) is previously set. (See 20.7.2 BDLC Control Register 1 for a better understanding of IE.) This results in less of a power saving, but the BDLC is guaranteed to receive correctly the message which woke it up, since the BDLC internal operating clocks are kept running.
AGREEMENT
NOTE:
Ensuring that all transmissions are complete or aborted before putting the BDLC into wait mode is important.
NON-DISCLOSURE
20.8.2 Stop Mode This power-conserving mode is entered automatically from run mode whenever the CPU executes a STOP instruction or if the CPU executes a WAIT instruction and the WCM bit in the BDLC control register 1 (BCR1) is previously set. This is the lowest power mode that the BDLC can enter. A subsequent passive-to-active transition on the J1850 bus will cause the BDLC to wake up and generate a non-maskable CPU interrupt request. When a STOP instruction is used to put the BDLC in stop mode, the BDLC is not guaranteed to correctly receive the message which woke it up, since it may take some time for the BDLC internal operating clocks to restart and stabilize. If a WAIT instruction is used to put the BDLC in stop mode, the BDLC is guaranteed to correctly receive the byte which woke it up, if and only if an end-of-frame (EOF) has been
Advance Information 368 Byte Data Link Controller-Digital (BDLC-D) MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Byte Data Link Controller-Digital (BDLC-D) Low-Power Modes
detected prior to issuing the WAIT instruction by the CPU. Otherwise, the BDLC will not correctly receive the byte that woke it up. If this mode is entered while the BDLC is receiving a message, the first subsequent received edge will cause the BDLC to wake up immediately, generate a CPU interrupt request, and wait for the BDLC internal operating clocks to restart and stabilize before normal communications can resume. Therefore, the BDLC is not guaranteed to receive that message correctly.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Byte Data Link Controller-Digital (BDLC-D)
Advance Information 369
NON-DISCLOSURE
AGREEMENT
NOTE:
It is important to ensure all transmissions are complete or aborted prior to putting the BDLC into stop mode.
REQUIRED
Byte Data Link Controller-Digital (BDLC-D) REQUIRED NON-DISCLOSURE
Advance Information 370 Byte Data Link Controller-Digital (BDLC-D)
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 21. Electrical Specifications
21.1 Contents
21.2 21.3 21.4 21.5 21.6 21.7 21.8 21.9 Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372 Functional Operating Range. . . . . . . . . . . . . . . . . . . . . . . . . .373 Thermal Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373 5.0-Volt DC Electrical Characteristics Control Timing . . . . . .374 Control Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375 ADC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376 5.0-Vdc 10% Serial Peripheral Interface (SPI) Timing. . . . .377 CGM Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . .380 . . . . . . . . . . . . . . . . . . . . . . .380
21.10 CGM Component Information
21.12 Timer Module Characteristics . . . . . . . . . . . . . . . . . . . . . . . . .382 21.13 RAM Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382 21.14 EEPROM Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . .382 21.15 BDLC Transmitter VPW Symbol Timings . . . . . . . . . . . . . . . .382 21.16 BDLC Receiver VPW Symbol Timings . . . . . . . . . . . . . . . . . .383 21.17 BDLC Transmitter DC Electrical Characteristics . . . . . . . . . .384 21.18 BDLC Receiver DC Electrical Characteristics . . . . . . . . . . . .384
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications
Advance Information 371
NON-DISCLOSURE
21.11 CGM Acquisition/Lock Time Information
. . . . . . . . . . . . . . .381
AGREEMENT
REQUIRED
Electrical Specifications REQUIRED 21.2 Maximum Ratings
Maximum ratings are the extreme limits to which the MCU can be exposed without permanently damaging it. The MCU contains circuitry to protect the inputs against damage from high static voltages; however, do not apply voltages higher than those shown in the table below. Keep VIN and VOUT within the range VSS (VIN or VOUT) VDD. Connect unused inputs to the appropriate voltage level, either VSS or VDD.
Rating Supply Voltage Input Voltage Maximum Current Per Pin Excluding VDD and VSS Storage Temperature Maximum Current out of VSS Maximum Current into VDD Reset IRQ Input Voltage Symbol VDD VIN I TSTG IMVSS IMVDD VHI Value -0.3 to +6.0 VSS -0.3 to VDD +0.3 25 -55 to +150 100 100 VDD to VDD + 2 Unit V V mA C mA mA V
AGREEMENT
NON-DISCLOSURE
NOTE: Voltages are referenced to VSS.
NOTE:
This device is not guaranteed to operate properly at the maximum ratings. Refer to 21.5 5.0-Volt DC Electrical Characteristics Control Timing for guaranteed operating conditions.
Advance Information 372 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrical Specifications Functional Operating Range
21.3 Functional Operating Range
Rating Operating Temperature Range Operating Voltage Range Symbol TA VDD Value -40 to 105 5.0 10% Unit C V
21.4 Thermal Characteristics
Characteristic Thermal Resistance PLCC (52 Pins) I/O Pin Power Dissipation Power Dissipation(1) Constant(2) Average Junction Temperature Maximum Junction Temperature Symbol JA PI/O PD K TJ TJM Value 50 User Determined PD = (IDD x VDD) + PI/O = K/(TJ + 273 C) PD x (TA + 273 C) + (PD2 x JA) TA = PD Unit C/W W W W/C C C
x JA
150
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications
Advance Information 373
NON-DISCLOSURE
1. Power dissipation is a function of temperature 2. K is a constant unique to the device. K can be determined from a known TA and measured PD. With this value of K, PD and TJ can be determined for any value of TA.
AGREEMENT
REQUIRED
Electrical Specifications REQUIRED 21.5 5.0-Volt DC Electrical Characteristics Control Timing
Characteristic(1) Output High Voltage (ILoad = -2.0 mA) All Ports, RESET Output Low Voltage (ILoad = 1.6 mA) All Ports, RESET Input High Voltage All Ports, IRQs, RESET, OSC1 Input Low Voltage All Ports, IRQs, RESET, OSC1 VDD + VDDA/VDDAREF Supply Current Run(3) Wait(4) Stop(5) 25 C -40 C to +105 C 25 C with LVI Enabled -40 C to +105 C with LVI Enabled I/O Ports Hi-Z Leakage Current Input Current Capacitance Ports (As Input or Output) Low-Voltage Reset Inhibit Symbol VOH VOL VIH VIL Min VDD -0.8 -- 0.7 x VDD VSS -- -- IDD -- -- -- -- -- -- -- -- 3.7 50 0 0 0.02 VDD Typ(2) -- -- -- -- Max -- 0.4 VDD 0.3 x VDD 30 15 5 50 400 500 1 1 12 8 4.45 -- 200 800 -- VDD + 2 Unit V V V V
AGREEMENT
-- -- -- -- -- -- -- -- -- -- 4.1 150 -- -- --
mA mA A A A A A A pF V mV mV mV V/ms V
IL IIN COUT CIN VLVF HLVI VPOR VPORRST RPOR VHI
NON-DISCLOSURE
Low-Voltage Reset Inhibit/Recover Hysteresis POR ReArm Voltage(6) POR Reset Voltage(7) Voltage(9) POR Rise Time Ramp Rate(8) High COP Disable
1. VDD = 5.0 Vdc 10%, VSS = 0 Vdc, TA = -40 C to +105 C, unless otherwise noted. 2. Typical values reflect average measurements at midpoint of voltage range, 25 C only. 3. Run (Operating) IDD measured using external square wave clock source (fOP = 8.4 MHz). All inputs 0.2 V from rail. No dc loads. Less than 100 pF on all outputs. CL = 20 pF on OSC2. All ports configured as inputs. OSC2 capacitance linearly affects run IDD. Measured with all modules enabled. 4. Wait IDD measured using external square wave clock source (fOP = 8.4 MHz). All inputs 0.2 Vdc from rail. No dcloads. Less than 100 pF on all outputs, CL = 20 pF on OSC2. All ports configured as inputs. OSC2 capacitance linearly affects wait IDD. Measured with all modules enabled. 5. Stop IDD measured with OSC1 = VSS. 6. Maximum is highest voltage that POR is guaranteed. 7. Maximum is highest voltage that POR is possible. 8. If minimum VDD is not reached before the internal POR reset is released, RST must be driven low externally until minimum VDD is reached. 9. See 13.9 COP Module During Break Interrupts.
Advance Information 374 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrical Specifications Control Timing
21.6 Control Timing
Characteristic(1) Bus Operating Frequency (4.5-5.5 V -- VDD Only) RESET Pulse Width Low IRQ Interrupt Pulse Width Low (Edge-Triggered) IRQ Interrupt Pulse Period EEPROM Programming Time per Byte EEPROM Erasing Time per Byte EEPROM Erasing Time per Block EEPROM Erasing Time per Bulk EEPROM Programming Voltage Discharge Period 16-Bit Timer(3) Input Capture Pulse Width(2) Input Capture Period Symbol fBUS tRL tILHI tILIL tEEPGM tEBYTE tEBLOCK tEBULK tEEFPV tTH, tTL tTLTL Min -- 1.5 1.5
(2)
Max 8.4 -- -- -- -- -- -- -- -- -- --
Unit MHz tcyc tcyc tcyc ms
10 10 10 10 100 2
(4)
ms ms s tcyc
1. VDD = 5.0 Vdc 10%, VSS = 0 Vdc, TA = -40 C to +105 C, unless otherwise noted. 2. Refer to Table 16-3. Mode, Edge, and Level Selection and supporting note. 3. The 2-bit timer prescaler is the limiting factor in determining timer resolution. 4. The minimum period tTLTL or tILIL should not be less than the number of cycles it takes to execute the capture interrupt service routine plus TBD tcyc.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications
Advance Information 375
NON-DISCLOSURE
AGREEMENT
ms
REQUIRED
Electrical Specifications REQUIRED 21.7 ADC Characteristics
Characteristic Resolution Absolute Accuracy (VREFL = 0 V, VDDA = VREFH = 5 V 10%) Conversion Range(1) (see Note 1) Power-Up Time Min 8 -1 VREFL 16 -- Max 8 +1 VREFH 17 1 Unit Bits LSB V s A ADC Clock Cycles Includes Sampling Time Includes Quantization VREFL = VSSA Conversion Time Period Comments
AGREEMENT
Input Leakage(2) (see Note 3) Ports B and D Conversion Time Monotonicity Zero Input Reading Full-Scale Reading Sample Time(3) (see Note 2) Input Capacitance
16
17
Inherent within Total Error 00 FE 5 -- 500 k -0.3 01 FF -- 8 1.048 M VDD + 0.3 Hex Hex ADC Clock Cycles pF Hz V Not Tested Tested Only at 1 MHz VIN = VREFL VIN = VREFH
NON-DISCLOSURE
ADC Internal Clock Analog Input Voltage
1. VDD = 5.0 Vdc 10%, VSS = 0 Vdc, VDDA/VDDAREF = 5.0 Vdc 10%, VSSA = 0 Vdc, VREFH = 5.0 Vdc 10% 2. The external system error caused by input leakage current is approximately equal to the product of R source and input current. 3. Source impedances greater than 10 k adversely affect internal RC charging time during input sampling.
Advance Information 376 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrical Specifications 5.0-Vdc 10% Serial Peripheral Interface (SPI) Timing
21.8 5.0-Vdc 10% Serial Peripheral Interface (SPI) Timing
Num(1) Characteristic(2) Operating Frequency(3) Master Slave 1 2 3 4 Cycle Time Master Slave Enable Lead Time Enable Lag Time Clock (SCK) High Time Master Slave Clock (SCK) Low Time Master Slave Data Setup Time, Inputs Master Slave Data Hold Time, Inputs Master Slave Access Time, Slave(4) CPHA = 0 CPHA = 1 Slave Disable Time, Hold Time to High-Impedance State Enable Edge Lead Time to Data Valid(5) Master Slave Enable Edge Lead Time to Data Invalid Master Slave Data Valid Master (Before Capture Edge) Data Hold Time (Outputs) Master (After Capture Edge) Symbol fBUS(M) fBUS(S) tcyc(M) tcyc(S) tLEAD tLAG tW(SCKH)M tW(SCKH)S tW(SCKL)M tW(SCKL)S tSU(M) tSU(S) tH(M) tH(S) tA(CP0) tA(CP1) tDIS tEV(M) tEV(S) tEI(M) tEI(S) tV(M) tHO(M) Min fBUS/128 dc 2 1 15 15 100 50 100 50 45 5 0 15 0 0 -- -- -- 0 5 90 100 Max fBUS/2 fBUS 128 -- -- -- -- -- -- -- -- -- -- -- 40 20 25 10 40 -- -- ----Unit MHz
tcyc ns ns ns
5
ns
6
ns
7
ns
8 9 10
ns ns ns
11 12 13
ns ns ns
1. Item numbers refer to dimensions in Figure 21-1 and Figure 21-2. 2. All timing is shown with respect to 30% VDD and 70% VDD, unless otherwise noted; assumes 100 pF load on all SPI pins. 3. fBUS = the currently active bus frequency for the microcontroller. 4. Time to data active from high-impedance state 5. With 100 pF on all SPI pins
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications
Advance Information 377
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrical Specifications REQUIRED
SS (INPUT)
SS pin of master held high. 1
SCK (CPOL = 0) (OUTPUT)
NOTE
5 4
SCK (CPOL = 1) (OUTPUT)
NOTE
5 4 6 7 LSB IN 10 BITS 6-1 11 MASTER LSB OUT
MISO (INPUT)
MSB IN 10 11 MASTER MSB OUT 12 13
BITS 6-1
AGREEMENT
MOSI (OUTPUT)
NOTE: This first clock edge is generated internally, but is not seen at the SCK pin.
a) SPI Master Timing (CPHA = 0)
SS (INPUT)
SS pin of master held high. 1
NON-DISCLOSURE
SCK (CPOL = 0) (OUTPUT)
5 4
NOTE
SCK (CPOL = 1) (OUTPUT)
5 4 6 7 LSB IN 10 BITS 6-1 11 MASTER LSB OUT
NOTE
MISO (INPUT) 10 MOSI (OUTPUT)
MSB IN 11 MASTER MSB OUT 12 13
BITS 6-1
NOTE: This last clock edge is generated internally, but is not seen at the SCK pin.
b) SPI Master Timing (CPHA = 1)
Figure 21-1. SPI Master Timing
Advance Information 378 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrical Specifications 5.0-Vdc 10% Serial Peripheral Interface (SPI) Timing
SS (INPUT) 1 SCK (CPOL = 0) (INPUT) 2 SCK (CPOL = 1) (INPUT) 8 MISO (INPUT) SLAVE 6 MOSI (OUTPUT) MSB IN MSB OUT 7 10 BITS 6-1 BITS 6-1 11 LSB IN SLAVE LSB OUT 11 5 4 9 NOTE 11 5 4 3
NOTE: Not defined but normally MSB of character just received
a) SPI Slave Timing (CPHA = 0)
SS (INPUT) 1 SCK (CPOL = 0) (INPUT) 2 SCK (CPOL = 1) (INPUT) 8 MISO (OUTPUT) 5 4 10 NOTE SLAVE 6 MOSI (INPUT) MSB IN MSB OUT 7 10 BITS 6-1 BITS 6-1 11 LSB IN 9 SLAVE LSB OUT 5 4 3
NOTE: Not defined but normally LSB of character previously transmitted
b) SPI Slave Timing (CPHA = 1)
Figure 21-2. SPI Slave Timing
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications
Advance Information 379
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrical Specifications REQUIRED 21.9 CGM Operating Conditions
Characteristic Crystal Reference Frequency Range Nominal Multiplier VCO Center-of-Range Frequency(1) Medium Voltage VCO Center-of-Range Frequency Symbol fxclk fnom fvrs N L fvclk Min 1 -- 4.9152 4.9152 1 1 fvrsmin Typ -- 4.9152 -- -- -- -- -- Max 8 -- 32.8 16.4 15 15 fvrsmax Unit MHz MHz MHz MHz -- -- MHz
AGREEMENT
VCO Frequency Multiplier VCO Center-of-Range Multiplier VCO Operating Frequency
1. 5.0 V 10% VDD only
21.10 CGM Component Information
Characteristic Crystal (X1) Frequency (MHz)(1) Symbol fxclk CL C1 C2 RB RS CF Cbyp Min 1 -- -- -- -- 0 -- -- Typ 4.9152 -- 2 x CL 2 x CL 1 -- CFact x (VDDA/fxclk) 0.1 Max 8 -- -- -- -- 3.3 -- -- Unit MHz pF pF pF M k pF F
NON-DISCLOSURE
Crystal Load Capacitance(2) Crystal Fixed Capacitance(2) Crystal Tuning Capacitance(2) Feedback Bias Resistor Series Resistor(3) Filter Capacitor Bypass Capacitor(4)
1. Fundamental mode crystals only 2. Consult crystal manufacturer's data. 3. Not required 4. Cbyp must provide low AC impedance from f = fxclk/100 to 100 x fvclk, so series resistance must be considered.
Advance Information 380 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrical Specifications CGM Acquisition/Lock Time Information
21.11 CGM Acquisition/Lock Time Information
Description Filter Capacitor Multiply Factor Acquisition Mode Time Factor Tracking Mode Time Factor Manual Mode Time to Stable(1) Manual Stable to Lock Time(1) Manual Acquisition Time Tracking Mode Entry Frequency Tolerance Acquisition Mode Entry Frequency Tolerance LOCK Entry Frequency Tolerance LOCK Exit Frequency Tolerance Reference Cycles per Acquisition Mode Measurement Reference Cycles per Tracking Mode Measurement Automatic Mode Time to Stable(1) Automatic Stable to Lock Time(1) Automatic Lock Time PLL Jitter(2) Symbol Cfact Kacq Ktrk tacq tal tLock trk acq Lock unl nacq ntrk tacq tal tLock fJ Min -- -- -- -- Typ 0.0154 0.1135 0.0174 8 x V DDA ----------------------------f xclk x K acq
4 x V DDA --------------------------f xclk x K trk
Max -- -- -- --
Unit F/sV V V s
-- -- 0 6.3% 0 0.9% -- -- n acq ----------f xclk n trk ---------f xclk -- 0
-- -- 3.6% 7.2% 0.9% 1.8% -- -- --
s s -- -- -- -- Cyc Cyc s
tacq + tal -- -- -- -- 32 128 8 x V DDA ----------------------------f xclk x K acq
4 x V DDA --------------------------f xclk x K trk
-- -- fcrys x 0.025% x 2PN/4
s s Hz
tacq + tal --
1. If CF chosen correctly 2. Deviation of average bus frequency over 2 ms, N = VCO frequency multiplier
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications
Advance Information 381
NON-DISCLOSURE
AGREEMENT
REQUIRED
Electrical Specifications REQUIRED 21.12 Timer Module Characteristics
Characteristic Input Capture Pulse Width Input Clock Pulse Width Symbol tTIH, tTIL tTCH, tTCL Min 125 (1/fOP) + 5 Max -- -- Unit ns ns
21.13 RAM Characteristics
Characteristic RAM Data Retention Voltage Symbol VRDR Min 0.7 Max -- Unit V
AGREEMENT
21.14 EEPROM Characteristics
Characteristic EEPROM Write/Erase Cycles @ 10 ms Write Time + 85 C EEPROM Data Retention After 10,000 Write/Erase Cycles Value 10,000 10 Unit Cycles Years
NON-DISCLOSURE
21.15 BDLC Transmitter VPW Symbol Timings
Characteristic(1), Passive Logic 0 Passive Logic 1 Active Logic 0 Active Logic 1 Start-of-Frame (SOF) End-of-Data (EOD) End-of-Frame (EOF) Inter-Frame Separator (IFS)
(2)
Number 10 11 12 13 14 15 16 17
Symbol tTVP1 tTVP2 tTVA1 tTVA2 tTVA3 tTVP3 tTV4 tTV6
Min 62 126 126 62 198 198 278 298
Typ 64 128 128 64 200 200 280 300
Max 66 130 130 66 202 202 282 302
Unit s s s s s s s s
1. fBDLC = 1.048576 or 1.0 MHz, VDD = 5.0 V 10%, VSS = 0 V 2. See Figure 21-3.
Advance Information 382 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Electrical Specifications BDLC Receiver VPW Symbol Timings
21.16 BDLC Receiver VPW Symbol Timings
Characteristic(1), Passive Logic 0 Passive Logic 1 Active Logic 0 Active Logic 1 Start-of-Frame (SOF) End-of-Data (EOD) End-of-Frame (EOF) Break
(2), (3)
Number 10 11 12 13 14 15 16 18
Symbol tTRVP1 tTRVP2 tTRVA1 tTRVA2 tTRVA3 tTRVP3 tTRV4 tTRV6
Min 34 96 96 34 163 163 239 280
Typ 64 128 128 64 200 200 280 --
Max 96 163 163 96 239 239 320 --
Unit s s s s s
s s
1. fBDLC = 1.048576 or 1.0 MHz, VDD = 5.0 V 10%, VSS = 0 V 2. The receiver symbol timing boundaries are subject to an uncertainty of 1 tBDLC s due to sampling considerations. 3. See Figure 21-3.
14
10
12
SOF
0
0
13
11
15
1
1
0
EOD
16
EOF 18
BRK
Figure 21-3. BDLC Variable Pulse Width Modulation (VPW) Symbol Timing
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Electrical Specifications Advance Information 383
NON-DISCLOSURE
AGREEMENT
s
REQUIRED
Electrical Specifications REQUIRED 21.17 BDLC Transmitter DC Electrical Characteristics
Characteristic(1) BDTxD Output Low Voltage (IBDTxD = 1.6 mA) BDTxD Output High Voltage (IBDTx = -800 A) Symbol VOLTX VOHTX Min -- VDD -0.8 Max 0.4 -- Unit V V
1. VDD = 5.0 Vdc + 10%, VSS = 0 Vdc, TA = -40 oC to +125 oC, unless otherwise noted
AGREEMENT
21.18 BDLC Receiver DC Electrical Characteristics
Characteristic(1) BDRxD Input Low Voltage BDRxD Input High Voltage BDRxD Input Low Current BDRxD Input High Current Symbol VILRX VIHRX IILBDRXI IHBDRX Min VSS 0.7 x VDD -1 -1 Max 0.3 x VDD VDD +1 +1 Unit V V A A
1. VDD = 5.0 Vdc + 10%, VSS = 0 Vdc, TA = -40 oC to +125 oC, unless otherwise noted
NON-DISCLOSURE
Advance Information 384 Electrical Specifications
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 22. Mechanical Data
22.1 Contents
22.2 22.3 22.4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 52-Pin Plastic Leaded Chip Carrier Package (Case 778) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386 64-Pin Quad Flat Pack (Case 840B) . . . . . . . . . . . . . . . . . . .387
22.2 Introduction
This section describes the dimensions of the 52-pin plastic leaded chip carrier (PLCC) package and the 64-pin quad flat pack (QFP).
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Mechanical Data
Advance Information 385
NON-DISCLOSURE
AGREEMENT
REQUIRED
Mechanical Data REQUIRED 22.3 52-Pin Plastic Leaded Chip Carrier Package (Case 778)
B -N- Y BRK D Z -L- -M-
0.007 (0.18) U
M
T L-M
M
S
N
S S
0.007 (0.18)
T L-M
N
S
AGREEMENT
W D
52 1
X V VIEW D-D 0.007 (0.18) 0.007 (0.18)
M
G1 0.010 (0.25)
S
T L-M
S
N
S
A Z R
T L-M T L-M
S
N N
S
M
S
S
E C G G1 J VIEW S T L-M N 0.004 (0.100) -T- SEATING
PLANE
NON-DISCLOSURE
0.010 (0.25)
S
S
S
H K1
0.007 (0.18)
M
T L-M
S
N
S
NOTES: 1. DATUMS -L-, -M-, AND -N- DETERMINED WHERE TOP OF LEAD SHOULDER EXITS PLASTIC BODY AT MOLD PARTING LINE. 2. DIMENSION G1, TRUE POSITION TO BE MEASURED AT DATUM -T-, SEATING PLANE. 3. DIMENSIONS R AND U DO NOT INCLUDE MOLD FLASH. ALLOWABLE MOLD FLASH IS 0.010 (0.250) PER SIDE. 4. DIMENSIONING AND TOLERANCING PER ANSI Y14.5M, 1982. 5. CONTROLLING DIMENSION: INCH. 6. THE PACKAGE TOP MAY BE SMALLER THAN THE PACKAGE BOTTOM BY UP TO 0.012 (0.300). DIMENSIONS R AND U ARE DETERMINED AT THE OUTERMOST EXTREMES OF THE PLASTIC BODY EXCLUSIVE OF MOLD FLASH, TIE BAR BURRS, GATE BURRS AND INTERLEAD FLASH, BUT INCLUDING ANY MISMATCH BETWEEN THE TOP AND BOTTOM OF THE PLASTIC BODY. 7. DIMENSION H DOES NOT INCLUDE DAMBAR PROTRUSION OR INTRUSION. THE DAMBAR PROTRUSION(S) SHALL NOT CAUSE THE H DIMENSION TO BE GREATER THAN 0.037 (0.940). THE DAMBAR INTRUSION(S) SHALL NOT CAUSE THE H DIMENSION TO BE SMALLER THAN 0.025 (0.635). INCHES MIN MAX 0.785 0.795 0.785 0.795 0.165 0.180 0.090 0.110 0.013 0.019 0.050 BSC 0.026 0.032 0.020 --- 0.025 --- 0.750 0.756 0.750 0.756 0.042 0.048 0.042 0.048 0.042 0.056 --- 0.020 2_ 10 _ 0.710 0.730 0.040 --- MILLIMETERS MIN MAX 19.94 20.19 19.94 20.19 4.20 4.57 2.29 2.79 0.33 0.48 1.27 BSC 0.66 0.81 0.51 --- 0.64 --- 19.05 19.20 19.05 19.20 1.07 1.21 1.07 1.21 1.07 1.42 --- 0.50 2_ 10 _ 18.04 18.54 1.02 ---
K VIEW S
F
0.007 (0.18)
M
T L-M
S
N
S
DIM A B C E F G H J K R U V W X Y Z G1 K1
Advance Information 386 Mechanical Data
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Mechanical Data 64-Pin Quad Flat Pack (Case 840B)
22.4 64-Pin Quad Flat Pack (Case 840B)
L
48 49 33 32 S S
0.05 (0.002) A-B
B B P
C A-B
-A- L
-B- B
-A-, -B-, -D-
DETAIL A
DETAIL A
64 17
1
F
16
-D- A 0.20 (0.008)
M
C A-B
S
D
S
J
N
0.05 (0.002) A-B S 0.20 (0.008) M H A-B E
S
D M
S
D DETAILC 0.02 (0.008)
M
BASE METAL
C A-B
S
D
S
C -C-
SEATING PLANE
-H- H M G
DATUM PLANE
0.01 (0.004)
U T R -H-
DATUM PLANE
Q K W X DETAIL C
NOTES: 1. DIMENSIONING AND TOLERANCING PER ANSI Y14.5M, 1982. 2. CONTROLLING DIMENSION: MILLIMETER. 3. DATUM PLANE -H- IS LOCATED AT BOTTOM OF LEAD AND IS COINCIDENT WITH THE LEAD WHERE THE LEAD EXITS THE PLASTIC BODY AT THE BOTTOM OF THE PARTING LINE. 4. DATUMS -A-, -B- AND -D- TO BE DETERMINED AT DATUM PLANE -H-. 5. DIMENSIONS S AND V TO BE DETERMINED AT SEATING PLANE -C-. 6. DIMENSIONS A AND B DO NOT INCLUDE MOLD PROTRUSION. ALLOWABLE PROTRUSION IS 0.25 (0.010) PER SIDE. DIMENSIONS A AND B DO INCLUDE MOLD MISMATCH AND ARE DETERMINED AT DATUM PLANE -H-. 7. DIMENSION D DOES NOT INCLUDE DAMBAR PROTRUSION. ALLOWABLE DAMBAR PROTRUSION SHALL BE 0.08 (0.003) PER SIDE. TOTAL IN EXCESS OF THE D DIMENSION AT MAXIMUM MATERIAL CONDITION. DAMBAR CANNOT BE LOCATED ON THE LOWER RADIUS OR THE FOOT.
DIM A B C D E F G H J K L M N P Q R S T U V W X
MILLIMETERS MIN MAX 13.90 14.10 13.90 14.10 2.15 2.45 0.30 0.45 2.00 2.40 0.30 0.40 0.80 BSC --- 0.25 0.13 0.23 0.65 0.95 12.00 REF 5_ 10_ 0.13 0.17 0.40 BSC 0_ 7_ 0.13 0.30 16.95 17.45 0.13 --- 0_ --- 16.95 17.45 0.35 0.45 1.6 REF
INCHES MIN MAX 0.547 0.555 0.547 0.555 0.085 0.096 0.012 0.018 0.079 0.094 0.012 0.016 0.031 BSC --- 0.010 0.005 0.009 0.026 0.037 0.472 REF 5_ 10_ 0.005 0.007 0.016 BSC 0_ 7_ 0.005 0.012 0.667 0.687 0.005 --- 0_ --- 0.667 0.687 0.014 0.018 0.063 REF
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Mechanical Data
Advance Information 387
NON-DISCLOSURE
AGREEMENT
V
M
0.20 (0.008)
0.20 (0.008)
M
H A-B
REQUIRED
D
S
S
D
Mechanical Data REQUIRED NON-DISCLOSURE
Advance Information 388 Mechanical Data
AGREEMENT
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Advance Information -- MC68HC08AS32
Section 23. Ordering Information
23.1 Contents
23.2 23.3 23.4 23.5 23.6 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389 MCU Ordering Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389 Application Program Media. . . . . . . . . . . . . . . . . . . . . . . . . . .390 ROM Program Verification . . . . . . . . . . . . . . . . . . . . . . . . . . .391 MC Order Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392
23.2 Introduction
This section contains instructions for ordering custom-masked ROM MCUs.
23.3 MCU Ordering Forms
To initiate an order for a ROM-based MCU, first obtain the current ordering form for the MCU from a Motorola representative. Submit the following items when ordering MCUs: * * * A current MCU ordering form that is completely filled out (Contact your Motorola sales office for assistance.) A copy of the customer specification if the customer specification deviates from the Motorola specification for the MCU Customer's application program on one of the media listed in 23.4 Application Program Media.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Ordering Information
Advance Information 389
NON-DISCLOSURE
AGREEMENT
REQUIRED
Ordering Information REQUIRED
The current MCU ordering form is available also through the Motorola Freeware Bulletin Board Service (BBS). The telephone number is (512) 895-FREE. After making the connection, type bbs in lowercase letters. Then press the return key to start the BBS software.
23.4 Application Program Media
Please deliver the application program to Motorola in one of these:
AGREEMENT
* * *
Macintosh(R)1 3 1/2-inch diskette (double-sided 800 K or double-sided high-density 1.4 M) MS-DOS(R)2 or PC-DOSTM3 3 1/2-inch diskette (double-sided 720 K or double-sided high-density 1.44 M) MS-DOS(R) or PC-DOSTM 5 1/4-inch diskette (double-sided double-density 360 K or double-sided high-density 1.2 M)
Use positive logic for data and addresses. When submitting the application program on a diskette, clearly label the diskette with this information: * * * * * * * Customer name Customer part number Project or product name File name of object code Date Name of operating system that formatted diskette Formatted capacity of diskette
NON-DISCLOSURE
1. Macintosh is a registered trademark of Apple Computer, Inc. 2. MS-DOS is a registered trademark of Microsoft Corporation. 3. PC-DOS is a trademark of International Business Machines Corporation.
Advance Information 390 Ordering Information
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Ordering Information ROM Program Verification
On diskettes, the application program must be in Motorola's S-record format (S1 and S9 records), a character-based object file format generated by M6805 cross assemblers and linkers. Begin the application program at the first user ROM location. Program addresses must correspond exactly to the available on-chip user ROM addresses as shown in the memory map. Write $00 in all non-user ROM locations or leave all non-user ROM locations blank. Refer to the current MCU ordering form for additional requirements. Motorola may request pattern resubmission if non-user areas contain any non-zero code. If the memory map has two user ROM areas with the same addresses, then write the two areas in separate files on the diskette. Label the diskette with both file names. In addition to the object code, a file containing the source code can be included. Motorola keeps this code confidential and uses it only to expedite ROM pattern generation in case of any difficulty with the object code. Label the diskette with the file name of the source code.
23.5 ROM Program Verification
The primary use for the on-chip ROM is to hold the customer's application program. The customer develops and debugs the application program and then submits the MCU order along with the application program. Motorola enters the customer's application program code into a computer program that generates a listing verify file. The listing verify file represents the memory map of the MCU. The listing verify file contains the user ROM code and also may contain non-user ROM code, such as self-check code. Motorola sends the customer a computer printout of the listing verify file along with a listing verify form. To aid the customer in checking the listing verify file, Motorola programs the listing verify file into customer-supplied blank preformatted Macintosh or DOS disks. All original pattern media are filed for contractual purposes and are not returned.
MC68HC08AS32 -- Rev. 3.0 MOTOROLA Ordering Information
Advance Information 391
NON-DISCLOSURE
AGREEMENT
REQUIRED
Ordering Information REQUIRED
Check the listing verify file thoroughly, then complete and sign the listing verify form and return the listing verify form to Motorola. The signed listing verify form constitutes the contractual agreement for the creation of the custom mask.
23.6 MC Order Numbers
Table 23-1. MC Order Numbers
AGREEMENT
MC Order Number
MC68HC08AS32FN(1) MC68HC08AS32CFN MC68HC08AS32VFN MC68HC08AS32FU(2) MC68HC08AS32CFU MC68HC08AS32VFU 1. FN = plastic leaded chip carrier 2. FU = quad flat pack
Operating Temperature Range
0 C to + 70 C - 40 C to + 85 C - 40 C to + 105 C 0 C to + 70 C - 40 C to + 85 C - 40 C to + 105 C
NON-DISCLOSURE
Advance Information 392 Ordering Information
MC68HC08AS32 -- Rev. 3.0 MOTOROLA
Motorola reserves the right to make changes without further notice to any products herein. Motorola makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does Motorola assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. "Typical" parameters which may be provided in Motorola data sheets and/or specifications can and do vary in different applications and actual performance may vary over time. All operating parameters, including "Typicals" must be validated for each customer application by customer's technical experts. Motorola does not convey any license under its patent rights nor the rights of others. Motorola products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other application in which the failure of the Motorola product could create a situation where personal injury or death may occur. Should Buyer purchase or use Motorola products for any such unintended or unauthorized application, Buyer shall indemnify and hold Motorola and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Motorola was negligent regarding the design or manufacture of the part. Motorola and are registered trademarks of Motorola, Inc. Motorola, Inc. is an Equal Opportunity/Affirmative Action Employer.
How to reach us: USA/EUROPE/Locations Not Listed: Motorola Literature Distribution, P.O. Box 5405, Denver, Colorado 80217, 1-800-441-2447 or 1-303-675-2140. Customer Focus Center, 1-800-521-6274 JAPAN: Nippon Motorola Ltd.: SPD, Strategic Planning Office, 141, 4-32-1 Nishi-Gotanda, Shinagawa-ku, Tokyo, Japan. 03-5487-8488 ASIA/PACIFIC: Motorola Semiconductors H.K. Ltd., 8B Tai Ping Industrial Park, 51 Ting Kok Road, Tai Po, N.T., Hong Kong. 852-26629298 MfaxTM, Motorola Fax Back System: RMFAX0@email.sps.mot.com; http://sps.motorola.com/mfax/; TOUCHTONE, 1-602-244-6609; US and Canada ONLY, 1-800-774-1848 HOME PAGE: http://motorola.com/sps/
Mfax is a trademark of Motorola, Inc. (c) Motorola, Inc., 1997
MC68HC08AS32/D


▲Up To Search▲   

 
Price & Availability of 68HC08AS32

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X